Only use parallel version avoidance for significants #183
Conversation
This file contains 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
Only if reckoning a significant version should we try to avoid version numbers tagged on parallel branches. This is in line with our existing documented axioms (which focused on two TAGGED parallel versions). What this helps with is feature branches where you aren't intending to make a release, and there's more benefit to having the version logically related to what the history of the branch is, rather than assuming the feature branch will eventually conflict and try to eagerly avoid the existing parallel version.
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.
Only if reckoning a significant version should we try to avoid version numbers tagged on parallel branches. This is in line with our
existing documented axioms (which focused on two TAGGED parallel versions).
What this helps with is feature branches where you aren't intending to make a release, and there's more benefit to having the version logically related to what the history of the branch is, rather than assuming the feature branch will eventually conflict and try to eagerly avoid the existing parallel version.