[SERVER-35021] Pre-release version numbers are not ascending Created: 16/May/18  Updated: 27/Oct/23  Resolved: 31/May/18

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Robert Stam Assignee: Ramon Fernandez Marina
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

3.7.9 was released on April 27.

v3.7.9-224-gc23aaecb55 was released on May 10.

But according to semantic versioning rules for comparing version numbers:

v3.7.9-224-gc23aaecb55 < 3.7.9

which implies v3.7.9-224-gc23aaecb55 was released before 3.7.9, when in fact it was released after.

I think once 3.7.9 was released all future builds should be pre-release builds of 3.7.10 and not of 3.7.9.



 Comments   
Comment by Ramon Fernandez Marina [ 31/May/18 ]

We could tag the first commit after every X.Y.Z release with "X.Y.Z+1-pre", but I feel that will cause more confusion with the use of git describe that we have (and I fear may have tentacles in many tools already), so I'm going to close this ticket for the time being.

If others have another proposal that's amenable to automation please comment here, and we can re-discuss.

Thanks,
Ramón.

Comment by Robert Stam [ 16/May/18 ]

Even if we don't use semantic versioning for server releases, a version number of v3.7.9-224-gc23aaecb55 appears to be a pre-release version of 3.7.9, when in fact it comes after 3.7.9 and is actually a pre-release version of 3.7.10.

The current format is fine. It's just the "3.7.9" part that's causing confusion. Once 3.7.9 has been released we shouldn't be using "3.7.9" any more IMO.

Comment by Ramon Fernandez Marina [ 16/May/18 ]

The server doesn't really follow semantic versioning to the letter, so there's no requirement that we label our pre-releases one way or the other.

For pragmatic reasons and to help with automation, we use git describe to inject versions on binaries, so the current format is expected and there are no plans to change it at the moment.

Regards,
Ramón.

Generated at Thu Feb 08 04:38:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.