Differences between revisions 3410 and 3411
Revision 3410 as of 2019-06-12 18:25:00
Size: 3957
Editor: JaapKeuter
Comment: Make 2.4 EOL explicit.
Revision 3411 as of 2019-06-24 17:07:25
Size: 4036
Editor: GeraldCombs
Comment: Schedule 3.1.0.
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
 || 3.1.0 || July 18, 2019 || First development release for the 3.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



    July 17, 2019

    Next maintenance release of the 3.0 branch


    July 17, 2019

    Next maintenance release of the 2.6 branch


    July 17, 2019

    (Probably) last maintenance release of the 2.4 branch


    July 18, 2019

    First development release for the 3.2 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

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: https://abi-laboratory.pro/tracker/timeline/wireshark/)

    • Run tools/git-compare-abis.sh in the Git repository right before the release

    • Bump library versions as needed based on Libtool's documentation in */Makefile.am 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

  • Include Lua API changes in release notes (Lua dissectors can detect Wireshark version using get_version() and adjust the API used.)
  • 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 2019-06-24 17:07:25 by GeraldCombs)