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?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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,previewandpreview releaseAlpha:
alpha,aBeta:
beta,bDevelopment:
dev,dRelease Candidate:
rc,r,release,rcandidateFinal Release:
f,final,final_releaseMilestone:
ms,milestoneIs it within the scope of semver to specify a recommended use/abbreviation?
@haacked commented on GitHub (Dec 20, 2012):
Closing this as a dupe of 56
@haacked commented on GitHub (Feb 12, 2014):
WHoops. This is a dupe of #53 not 56