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.

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

doc: add instructions to only sign a release #5876

Closed
wants to merge 1 commit into from

Conversation

Fishrock123
Copy link
Contributor

Pull Request check-list

Affected core subsystem(s)

doc

Description of change

I didn't know this existed since it wasn't documented, but after some digging into the script itself this totally saved me today after I did release things out-of-order. 😓

@Fishrock123 Fishrock123 added the doc Issues and PRs related to the documentations. label Mar 23, 2016
@@ -246,6 +246,8 @@ Use `tools/release.sh` to promote and sign the build. When run, it will perform

If you didn't wait for ARM builds in the previous step before promoting the release, you should re-run `tools/release.sh` after the ARM builds have finished. That will move the ARM artifacts into the correct location. You will be prompted to re-sign SHASUMS256.txt.

Note: if you forgot to push the tag before promoting the builds, you can tell the script to only sign a particular release by running `./tools/release.sh -s vX.Y.Z`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: may be reasons other than forgetting for signing after the fact. Perhaps it should just note the option and ability to sign after promoting?

@MylesBorins
Copy link
Contributor

LGTM if you address the nit

@cjihrig
Copy link
Contributor

cjihrig commented Mar 23, 2016

LGTM

1 similar comment
@jasnell
Copy link
Member

jasnell commented Mar 23, 2016

LGTM

@Fishrock123
Copy link
Contributor Author

@thealphanerd updated, ptal.

@MylesBorins
Copy link
Contributor

LGTM

jasnell pushed a commit that referenced this pull request Mar 25, 2016
PR-URL: #5876
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
@jasnell
Copy link
Member

jasnell commented Mar 25, 2016

Landed in be68b68

@jasnell jasnell closed this Mar 25, 2016
evanlucas pushed a commit that referenced this pull request Mar 30, 2016
PR-URL: #5876
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
MylesBorins pushed a commit that referenced this pull request Mar 30, 2016
PR-URL: #5876
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
MylesBorins pushed a commit that referenced this pull request Mar 30, 2016
PR-URL: #5876
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
evanlucas pushed a commit that referenced this pull request Mar 31, 2016
PR-URL: #5876
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants