mirror of
https://github.com/semver/semver.git
synced 2026-07-11 05:12:48 -05:00
Question: how to name subsequent beta releases #383
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/semver#383
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tooomm on GitHub (May 20, 2019).
Hello, I'm not exactly sure about naming pre-releases, and want to make sure to follow the semver style correctly.
In the example for rule 11 it says
1.0.0-beta < 1.0.0-beta.2So do I have to skip -beta.1 because -beta implies that and I go on with -beta.2 directly?
Is there a rule at all? Because for alpha the example says
1.0.0-alpha < 1.0.0-alpha.1Could I start with -beta.1 as well and skip -beta?
I'm a bit confused on how to do it right. :)
@runeimp commented on GitHub (May 20, 2019):
@tooomm It's up to you how you name your pre-releases. It just needs to be sortable numerically if if it's number based pre-release version label or lexically (alphabetically) if it's a character or mixed character and number string. The alpha, beta, etc. is just a common example.
@tooomm commented on GitHub (May 20, 2019):
Ok. Thank you.
So alpha < beta < beta.2 < beta.3 is totally fine 👍
@jwdonahue commented on GitHub (Aug 16, 2019):
The example simply pointed out that tags with fewer dotted separated fields sort lower than tags with more dot separated fields. So: alpha < beta < beta.1 < beta.2 < beta.3.
Unless you have further questions, please close this thread at your earliest possible convenience.