This wiki has been migrated to and is now deprecated. Please use that site instead.
Differences between revisions 3353 and 3355 (spanning 2 versions)
Revision 3353 as of 2016-08-19 19:20:35
Size: 3427
Editor: GeraldCombs
Comment: More 2.2 dates.
Revision 3355 as of 2016-08-23 18:02:35
Size: 3474
Editor: GeraldCombs
Comment: 2.2.0rc1 has been released.
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
 || 2.2.0rc1 || August 22, 2016 || First release candidate for 2.2.0 ||
Line 16: Line 15:

  [[|Recent changes in the 2.2 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



    September 8, 2016

    Next maintenance release of the 2.0 branch


    August 31, 2016

    Second release candidate for 2.2.0


    September 7, 2016

    Final 2.2.0 release

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

For a list of bugs that should have been fixed before the 2.0 release, see Bugzilla (target milestone: 2.0 release).

Other proposed items (possibly out of date, see wiki source):

  • 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/*.symbols)

    • When major library version bumps are needed *.CMakeList.txt-s have to be changed at two locations and debian/lib*N.* files have to be updated and renamed

  • 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)