Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add release channel automation #16677

Closed
brson opened this issue Aug 22, 2014 · 4 comments
Closed

Add release channel automation #16677

brson opened this issue Aug 22, 2014 · 4 comments
Assignees
@brson
Labels
P-medium Medium priority
Milestone
1.0 beta

Comments

@brson
Copy link
Contributor

brson commented Aug 22, 2014

Before 1.0 we want to change the release process to have multiple parallel release channels ('nightly', 'beta', 'stable', probably). This will require a bunch of new automation.
@brson brson mentioned this issue Aug 22, 2014
Closed
@brson brson self-assigned this Aug 22, 2014
@brson brson added this to the 1.0 milestone Sep 4, 2014
@brson brson added the P-high label Sep 4, 2014
brson added a commit to brson/rust that referenced this issue Sep 15, 2014
@brson
mk: Update how the build deals with version labels. rust-lang#16677
a3c27ea 
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
@brson brson mentioned this issue Sep 17, 2014
Closed
65 tasks
@brson
Copy link
Contributor Author

brson commented Jan 5, 2015

The automation for distribution is done, but for integration is not.

@aturon
Copy link
Member

aturon commented Jan 8, 2015

Nominating for beta milestone.

@pnkfelix
Copy link
Member

pnkfelix commented Jan 8, 2015

assigning 1.0-beta. (We could struggle on without it, but it makes more sense to get it deployed by that time).

@pnkfelix pnkfelix modified the milestones: 1.0 beta, 1.0 Jan 8, 2015
@brson brson mentioned this issue Mar 26, 2015
Closed
@brson
Copy link
Contributor Author

brson commented Mar 26, 2015

Lot's of work on this is finished. Remaining tasks are #23756 and #21149.

@pnkfelix
Copy link
Member

Closing this task and letting the remaining two bugs serve as the, well, remaining work.

@brson brson mentioned this issue Mar 26, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@brson brson

Labels
P-medium Medium priority
Projects
None yet
Milestone
1.0 beta
Development

No branches or pull requests
4 participants
@alexcrichton @brson @pnkfelix @aturon