Hey Michael :), On Tue, Jul 24, 2018 at 3:47 AM, <mcatanz...@gnome.org> wrote: > On Mon, Jul 23, 2018 at 6:45 PM, Carlos Garnacho <carl...@gnome.org> wrote: >> >> I might send more reminders in the future whenever it might get >> confusing, but changes like this within the cycle apply anytime in the >> future too. How semver and gnome cycles will be made to fit neatly is >> TBD, but rest assured there will be a 2.x series in time for freezes >> and stabilized with it. 2.1.x will be it for 3.30. > > > You could do semantic versioning (which has clear benefits) without odd > minor versions (which is going to be super confusing), surely?
Hmm, I see 2 ways to make that happen: - As usual, bump by 1 during unstable, bump by 1 for .0. The first bump may make sense (depends on whether there's actual API additions, tending to be scarce in Tracker), but the second bump would be rather artificial as there'd be no API additions or substantial modifications at the time. - Bump to next even number directly, suffix versions by "-alpha.X" or somesuch to convey they're pre-release. (we should probably do this even if bumping by 1) Reading point 7 in semver.org, of these two I find the second to fit better as there's no minor bumps without actual changes involved, but it's maybe a bit late for it now. If the R-T vastly prefers to avoid the confusion, I have stuff in the queue I can rush this cycle to make a 2.2 that'd make all of us happy for now. Cheers, Carlos _______________________________________________ release-team@gnome.org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.