Originally created by @Constancejackson98 on GitHub (Sep 23, 2020).
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
Originally created by @Constancejackson98 on GitHub (Sep 23, 2020).
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
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.
@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.
@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.
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 @Constancejackson98 on GitHub (Sep 23, 2020).
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.