mk: Update how the build deals with version labels. #16677 #17285
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
Adds a new configure flag, --release-channel, which determines how the version number should be augmented with a release label, as well as how the distribution artifacts will be named. This is entirely for use by the build automation. --release-channel can be either 'source', 'nightly', 'beta', or 'stable'. Here's a summary of the affect of these values on version number and artifact naming, respectively: * source - '0.12.0-pre', 'rust-0.12.0-pre-...' * nightly - '0.12.0-nightly', 'rust-nightly-...' * beta - '0.12.0-beta', 'rust-beta-...' * stable - '0.12.0', 'rust-0.12.0-...' Per http://discuss.rust-lang.org/t/rfc-impending-changes-to-the-release-process/508/1
|
We do need to remember to update the dist bots to pass |
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this pull request
Sep 17, 2014
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.
Adds a new configure flag, --release-channel, which determines how the version
number should be augmented with a release label, as well as how the distribution
artifacts will be named. This is entirely for use by the build automation.
--release-channel can be either 'source', 'nightly', 'beta', or 'stable'.
Here's a summary of the affect of these values on version number and
artifact naming, respectively:
Per http://discuss.rust-lang.org/t/rfc-impending-changes-to-the-release-process/508/1
The only immediate practical impact of this is that nightlies will now be versioned
0.12.0-nightlyinstead of0.12.0-pre-nightly.r? @alexcrichton