RELEASE-PROCEDURE.md: release candidate git tagging explained #17177
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To help anyone wanting to build/reproduce release candidates, this is the set git tag naming scheme to use. Similar to, but different, than the "normal" release tags to not be possible to mixup.
|
Side note: Why are you still sticking with CVS-style tags where dots weren't allowed? |
|
For consistency. I alone have lots of scripting based on this. I assume a few others do as well. |
I bet others as well, but that is not a technical reason. When Tomcat migrated off Subversion to Git I raised my voice to get rid off the CVS limitation for tags since Git plays along. No reason why curl shouldn't do as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To help anyone wanting to build/reproduce release candidates, this is the set git tag naming scheme to use. Similar to, but different, than the "normal" release tags to not be possible to mixup.