Skip to content
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

Conversation

misterdjules
Copy link

This is a first step in making the release process easier to use by multiple users.

Instead of using /home/tj on nodejs.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

@sam-github
Copy link

I haven't run this, but the change LGTM. I'll give it a run next week.

@cjihrig
Copy link

cjihrig commented Jul 14, 2015

LGTM too from a glance

misterdjules pushed a commit that referenced this pull request Jul 16, 2015
Use staging area on nodejs.org instead of TJ's account. Also pushes
release tag and branch to personal forks rather than joyent/node, which
makes errors have less impact.

Pushing release tags and branches is left as a manual step for the
release managers, when they decide the timing is best.

PR: #25638
PR-URL: #25638
Reviewed-By: Sam Roberts <sam@strongloop.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@misterdjules
Copy link
Author

Landed in ec861f6, thank you @sam-github and @cjihrig 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants