This wiki has been migrated to https://gitlab.com/wireshark/wireshark/-/wikis/home and is now deprecated. Please use that site instead.
Differences between revisions 1 and 2
Revision 1 as of 2008-04-24 07:29:45
Size: 1705
Editor: JaapKeuter
Comment: Basic description of Wireshark version numbering
Revision 2 as of 2008-04-25 17:22:06
Size: 2008
Editor: GeraldCombs
Comment: Add text about the build number and the format for prereleases.
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
The Wireshark release numbers are constructed as a three number tuple: '''`Major.Minor.Maintenance`'''. 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`'''.
Line 13: Line 15:
Before a release there may be prereleases, which are designated as such. The ''Build number'' is the source code repository revision number corresponding to that particular build.

Before a release there may be prereleases, which are designated with the word ''pre'' and a number, such as ''1.0.0pre2''.

Release numbers

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.

Before a release there may be prereleases, which are designated with the word pre and a number, such as 1.0.0pre2.

Example release number tree

This tree shows a release number assignment tree based on this algorithm. On the left the development tree is visible, while to the right the stable releases grow out. It's is like an upside down tree.

Ethereal
  |
  v
  +--> 0.99.8pre1--> 0.99.8
  |
  v
0.99.9
  |
  +--> 1.0.0pre1--> 1.0.0pre2--> 1.0.0--> 1.0.1--> etc
  |
  v
1.1.0
  |
  v
1.1.1 (If we have the need for an intermediate development version number)
  |
  +--> 1.2.0pre1--> 1.2.0pre2--> 1.2.0--> 1.2.1--> etc
  |
  v
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
  |
  v
2.1.0
 etc

Development/ReleaseNumbers (last edited 2020-07-12 15:09:49 by JaapKeuter)