mirror of
https://github.com/semver/semver.git
synced 2026-07-10 19:50:47 -05:00
[GH-ISSUE #64] Same as apache? More examples #6040
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/semver#6040
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 @Diaoul on GitHub (Jan 13, 2013).
Original GitHub issue: https://github.com/semver/semver/issues/64
I was using http://apr.apache.org/versioning.html which is pretty much the same as semver, I'm surprised there's not even a mention of it.
You could add some examples insipred by this document to semver.
@hwinkel commented on GitHub (Jan 19, 2013):
as it becomes more and more important to follow such versioning schemas I was thinking to publish a at least informal RFC about this. specially since semver has references to the RFC 2119. Semver could have a similar position as RFC 2119 and would not be part of an individual community. What do you think?
@haacked commented on GitHub (Mar 13, 2013):
@Diaoul I'm not sure that was an explicit inspiration. SemVer was inspired by existing practices so you might see many other similar predecessors. I suppose we could consider a page listing other versioning schemes, but I think that'd belong here: https://github.com/mojombo/semver.org
@hwinkel sounds like this would be better discussed as a separate issue. Mind opening one? I'll be honest, the thought never crossed my mind. Not sure what it entails or what it buys us, but I have an open mind. :)