This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
build: make release process usable by multiple users #25638
Closed
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 is a first step in making the release process easier to use by multiple users.
Instead of using
/home/tj
onnodejs.org
as a staging directory, it uses/home/staging
, which we also can control access to via ssh keys.Instead of pushing tags and branches directly to joyent/node, it pushes them to the personal fork of the person doing the release, so there's a chance to fix errors and mistakes before pushing tags and releases branches to the reference repository.
Finally it also now distinguishes between stable, maintenance and unstable versions to mirror the current v0.10/v0.12/v0.13 release lines.
These changes are in sync with the latest changes I made recently to the nodejs-release Jenkins job and Node.js release guide.
/cc @joyent/node-collaborators