mirror of
https://github.com/semver/semver.git
synced 2026-07-11 03:53:53 -05:00
[GH-ISSUE #618] Looking for help with systematic version labeling to properly move forward. #5554
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/semver#5554
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 @Constancejackson98 on GitHub (Sep 23, 2020).
Original GitHub issue: https://github.com/semver/semver/issues/618
I am looking for help from this team to keep moving forward with the repository. I am looking for help with labeling forward versions and to limit backward movement to prevent so many versions and branches that can cause an unstable proto type. Examples v 2.0, 2.1 2.20,ext. Also I need input as to how everyone would like this put to use. Thank you for your time and expertise
@klehelley commented on GitHub (Sep 24, 2020):
Could you please precise your question? What issue do you have that is specifically related to Semantic Versioning that would require a clarification in the specification or the resources surrounding it?
If your question is more general, or is related to SemVer but you feel you have understood the spec well, it is usually preferred that your question be asked on Stack Overflow with the "semver" tag. That will not stop some of us to answer here if you feel that is more convenient to you.
@Constancejackson98 commented on GitHub (Sep 24, 2020):
I do apologize first time posting and I was trying to follow the guidelines. I actually need alot of help and this was the 1st step of many that I could request help with. I will close this and check stack over-rflow.