release: Bump for 1.4 release cycle. #1414
Merged
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
jrick
approved these changes
Aug 21, 2018
This marks the start of a new release process as compared to previous releases. Instead of bumping the version just before a release and releasing from the master branch, as has been done up to this point, the minor (or major when necessary) will now be bumped on the master branch at the beginning of a release cycle. In addition, the pre-release portion of the semantic version is now the string "pre" to help make it more obvious that the master branch represents a pre-release build of work leading up to the next release. When a new release is prepared, a new release branch will be created that has a naming scheme of "release-vX.Y", where X is the major and Y is the minor. Any additional commits needed to prepare the release leading up to a release candidate will be cherry-picked to the release branch, and all tags for releases and release candidates will be created against that. This implies that should any additional patch releases be necessary, the relevant commits will also be cherry-picked to the release branch as needed, followed by a new release candidate for the patch release and the eventual patch release.
davecgh
force-pushed
the
release_bump_dev_version
branch
from
610d40f
to
a1985a4
Compare
alexlyp
approved these changes
Aug 21, 2018
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.
This marks the start of a new release process as compared to previous releases.
Instead of bumping the version just before a release and releasing from the master branch, as has been done up to this point, the minor (or major when necessary) will now be bumped on the master branch at the beginning of a release cycle. In addition, the pre-release portion of the semantic version is now the string "pre" to help make it more obvious that the master branch represents a pre-release build of work leading up to the next release.
When a new release is prepared, a new release branch will be created that has a naming scheme of "release-vX.Y", where X is the major and Y is the minor. Any additional commits needed to prepare the release leading up to a release candidate will be cherry-picked to the release branch, and all tags for releases and release candidates will be created against that.
This implies that should any additional patch releases be necessary, the relevant commits will also be cherry-picked to the release branch as needed, followed by a new release candidate for the patch release and the eventual patch release.