[GH-ISSUE #57] alpha segment standardization? #1779

Closed
opened 2026-04-20 09:22:41 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @xsist10 on GitHub (Dec 6, 2012).
Original GitHub issue: https://github.com/semver/semver/issues/57

Is there/should there be a standard for the alpha segments?

For instance I've seen

Preview: pre, pr, p, preview and preview release
Alpha: alpha, a
Beta: beta, b
Development: dev, d
Release Candidate: rc, r, release, rcandidate
Final Release: f, final, final_release
Milestone: ms, milestone

Is it within the scope of semver to specify a recommended use/abbreviation?

Originally created by @xsist10 on GitHub (Dec 6, 2012). Original GitHub issue: https://github.com/semver/semver/issues/57 Is there/should there be a standard for the alpha segments? For instance I've seen Preview: `pre`, `pr`, `p`, `preview` and `preview release` Alpha: `alpha`, `a` Beta: `beta`, `b` Development: `dev`, `d` Release Candidate: `rc`, `r`, `release`, `rcandidate` Final Release: `f`, `final`, `final_release` Milestone: `ms`, `milestone` Is it within the scope of semver to specify a recommended use/abbreviation?
Author
Owner

@haacked commented on GitHub (Dec 20, 2012):

Closing this as a dupe of 56

<!-- gh-comment-id:11555508 --> @haacked commented on GitHub (Dec 20, 2012): Closing this as a dupe of 56
Author
Owner

@haacked commented on GitHub (Feb 12, 2014):

WHoops. This is a dupe of #53 not 56

<!-- gh-comment-id:34927389 --> @haacked commented on GitHub (Feb 12, 2014): WHoops. This is a dupe of #53 not 56
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/semver#1779