This wiki has been migrated to and is now deprecated. Please use that site instead.
Differences between revisions 3331 and 3332
Revision 3331 as of 2015-09-01 17:30:33
Size: 2223
Editor: GeraldCombs
Comment: Schedule 1.99.9
Revision 3332 as of 2015-10-05 18:45:45
Size: 2244
Editor: GeraldCombs
Comment: Schedule the next round of releases.
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
 || 1.99.9 || September 2, 2015 || Next development release ||
 || 1.12.8 || Unscheduled || Next maintenance release of the 1.12 branch ||
 || 2.0rc1 || October 14, 2015 || First release candidate for Wireshark 2.0 ||
 || 1.12.8 || October 14, 2015 || Next maintenance release of the 1.12 branch ||


This is a tentative roadmap for the next stable releases of Wireshark. For more information on the Wireshark release lifecycle and on past releases see Development/LifeCycle.


  • Release

    Expected Date



    October 14, 2015

    First release candidate for Wireshark 2.0


    October 14, 2015

    Next maintenance release of the 1.12 branch

Backporting Changes

Significant bug fixes should be backported to each applicable stable branches after they are checked in to the master branch. You can follow development progress using the links below.

Proposed Changes

  • Items marked with {1} in the TODO list of Development/SNMP

  • Keep plugin API and ABI stable and versioned, so binary plugins will reliably work with more than one Wireshark version (ABI changes can be followed here: Upstream Tracker)

    • Run tools/ in the Git repository right before the release

    • Bump library versions as needed based on Libtool's documentation in */ and */CmakeList.txt (don't forget updating debian/wireshark-common.files and debian/wireshark-common.shlibs)

  • Version checking
  • Add privilege separation for dissection
  • Add thread/multiprocessor support

... well, maybe all the points mentioned in the WishList!


  • Security improvements (see also: Security)

    • Add privilege separation for POSIX environments (in progress)
    • Add a similar mechanism for the Windows environment
    • Enhance the API to make it easier to write secure code (e.g. add tvb_get_gstring())?

  • Documentation of library API's (e.g. wiretap)


Development/Roadmap (last edited 2020-07-03 15:42:04 by GeraldCombs)