intrigeri:
> - Check if we need to adjust our version numbering scheme.
> sajolida, can you please take the lead on this after we've made
> a decision on #14578?
I'm not sure I should "take the lead" now but in /contribute/calendar
I see:
* 2017-11-14: Release Tails 3.3 (bugfix release)
* 2018-01-16: Release 3.4? (Firefox 52.6, bugfix release)
* 2018-03-06: Release 3.5? (Firefox 52.7, major release)
* 2018-05-01: Release 3.6? (Firefox 52.8, bugfix release)
* 2018-06-26: Release 3.7? (Firefox 59.2, major release)
* 2018-08-21: Release 3.8? (Firefox 59.3, bugfix release)
* 2018-10-16: Release 3.9? (Firefox 59.4, major release)
* 2018-11-27: Release 3.10? (Firefox 59.5, bugfix release)
But if we want to keep the even=major odd=bugfix we should do:
* 2017-11-14: Release Tails 3.3 (bugfix release)
* 2018-01-16: Release 3.4 (Firefox 52.6, bugfix release)
* 2018-03-06: Release 3.6 (Firefox 52.7, major release)
* 2018-05-01: Release 3.7 (Firefox 52.8, bugfix release)
* 2018-06-26: Release 3.8 (Firefox 59.2, major release)
* 2018-08-21: Release 3.9 (Firefox 59.3, bugfix release)
* 2018-10-16: Release 3.10 (Firefox 59.4, major release)
* 2018-11-27: Release 3.11 (Firefox 59.5, bugfix release)
For the record, we agreed on using the scheme "even=major odd=bugfix" as
a trade-off which is easier to handle for developers and might make
sense for some of our power users even if it might imply in rare
occasions some jumps in version numbers (for example 3.4 followed by
3.6) which probably doesn't make sense to the vast majority of our users.
