Re: [Wireshark-dev] Release lifetime and version number changes?

2019-04-20 Thread Uli Heilmeier
+1 for having only two supported stable versions. One as a „long term support“ branch (e.g. 2.6 at the moment) and one „normal“ stable (eg. 3.0 atm or next 3.2) +1 for keeping odd minor numbers for development versions. Maybe having a monthly rolling release with latests features to have more

Re: [Wireshark-dev] Release lifetime and version number changes?

2019-04-20 Thread Ross Jacobs
@Jaap Every build is released to the public like 3.5, 3.6, 3.7, etc. Current stable is 3.7 and development version is 3.8. Based on the docs ( https://docs.python.org/3.8/), the dev branch is alpha stage as it version 3.8.0a3. Once it becomes stable, 3.9 will become the developing version. On