Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upmk: Update how the build deals with version labels. #16677 #17285
Conversation
This comment has been minimized.
This comment has been minimized.
|
We do need to remember to update the dist bots to pass |
This comment has been minimized.
This comment has been minimized.
|
r+ |
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this pull request
Sep 17, 2014
bors
merged commit a3c27ea
into
rust-lang:master
Sep 17, 2014
1 check failed
continuous-integration/travis-ci
The Travis CI build failed
Details
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.
brson commentedSep 15, 2014
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