Describe the development snapshot
Add info for automated builds.
|Deletions are marked like this.||Additions are marked like this.|
|Line 17:||Line 17:|
|Before a release there may be prereleases, which are designated with the word ''pre'' and a number, such as ''1.0.0pre2''.||== Release candidates and automated builds ==
Before a release there may be release candidates, which are designated with the abbreviation ''rc'' and a number, such as ''1.10.7rc1''.
Additionally [[https://www.wireshark.org/download/automated/|automated builds]] include a commit ID. For example, the version stamp for the file `Wireshark-win64-1.11.3-2383-gd685e9b.exe` means the following:
* This is a development release (11 is odd).
* There have been 2383 commits since the last minor release (1.11.2).
* This build was triggered by [[https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=d685e9b3fe8e2adee34159ddeddf43b616f35234|commit d685e9b]].
|Line 26:||Line 34:|
|Ethereal and older Wireshark releases
+--> 0.99.8pre1--> 0.99.8
|Older Wireshark releases
↓→ 0.99.8pre1 → 0.99.8
|Line 32:||Line 39:|
+--> 1.0.0pre1--> 1.0.0pre2--> 1.0.0--> 1.0.1--> etc
↓→ 1.0.0pre1 → 1.0.0pre2 → 1.0.0 → 1.0.1 → 1.0.…
|Line 36:||Line 43:|
|Line 38:||Line 45:|
+--> 1.2.0pre1--> 1.2.0pre2--> 1.2.0--> 1.2.1--> etc
1.3.0 (if this development significantly changes the program the Major number may bump)
+--> 2.0.0pre1--> 2.0.0.pre2--> 2.0.0--> 2.0.1--> etc
↓→ 1.2.0pre1 → 1.2.0pre2 → 1.2.0 → 1.2.1 → 1.2.…
1.9.0 (if Wireshark significantly changes the program the Major number may bump)
↓→ 2.0.0rc1 → 2.0.0rc2 → 2.0.0 → 2.0.1 → 2.0.…
Release number tuple
Official Wireshark release numbers are constructed as a three number tuple: Major.Minor.Maintenance.
In some cases, such as the file version for Windows executables, a build number may be present: Major.Minor.Maintenance.Build.
The Major release number has reached 1 after numerous years of development and is likely to remain that way for a while. Only when the program undergoes a significant change this number will increment.
The Minor release number basically follows an even/odd number scheme. For every official release an even number is assigned and the code is branched off for maintenance. The development continues on the next higher odd release number. Note that this development package is a moving target and meaningless without its subversion revision number.
The Maintenance release number gives you the stage of maintenance which that release is in. It starts of with 0 and increments with every maintenance release.
The Build number is the source code repository revision number corresponding to that particular build.
Release candidates and automated builds
Before a release there may be release candidates, which are designated with the abbreviation rc and a number, such as 1.10.7rc1.
Additionally automated builds include a commit ID. For example, the version stamp for the file Wireshark-win64-1.11.3-2383-gd685e9b.exe means the following:
- This is a development release (11 is odd).
- There have been 2383 commits since the last minor release (1.11.2).
This build was triggered by commit d685e9b.
During development it may be desirable to have more exposure of newly implemented features. Although the development builds are available for everyone to download occasionally a development snapshot will be released. Note that these aren't branched off from the development tree, nor maintained. To indicate that development continues the Maintenance release number will be incremented.
Example release number tree
This tree shows a release number assignment tree based on this algorithm. On the left the main development trunk follows the down arrows, while the right arrows indicate stable release branches. It's is like an upside down tree.
Older Wireshark releases ↓ ↓→ 0.99.8pre1 → 0.99.8 ↓ 0.99.9 ↓ ↓→ 1.0.0pre1 → 1.0.0pre2 → 1.0.0 → 1.0.1 → 1.0.… ↓ 1.1.0 (a development snapshot may be released, which will not be branched off) ↓ 1.1.1 ↓ ↓→ 1.2.0pre1 → 1.2.0pre2 → 1.2.0 → 1.2.1 → 1.2.… … 1.9.0 (if Wireshark significantly changes the program the Major number may bump) ↓ ↓→ 2.0.0rc1 → 2.0.0rc2 → 2.0.0 → 2.0.1 → 2.0.… ↓ 2.1.0 etc