Schedule 2.2.4 and 2.0.10.
Schedule 2.2.5 and 2.0.11.
|Deletions are marked like this.||Additions are marked like this.|
|Line 6:||Line 6:|
| || 2.2.4 || January 25, 2016 || Next maintenance release of the 2.2 branch ||
|| 2.0.10 || January 25, 2016 || Next maintenance release of the 2.0 branch ||
| || 2.2.5 || March 2, 2016 || Next maintenance release of the 2.2 branch ||
|| 2.0.11 || March 2, 2016 || Next maintenance release of the 2.0 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.
March 2, 2016
Next maintenance release of the 2.2 branch
March 2, 2016
Next maintenance release of the 2.0 branch
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.
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 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
- 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)