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

doc: put release script specifics in details #35260

Closed
wants to merge 2 commits into from
Closed

doc: put release script specifics in details #35260

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5f121c9
doc: put release script specifics in details
MylesBorins Sep 18, 2020
bb13292
Update doc/guides/releases.md
MylesBorins Sep 20, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 2 additions & 0 deletions doc/guides/releases.md
View file
Open in desktop
Expand Up @@ -598,6 +598,7 @@ $ ./tools/release.sh -i ~/.ssh/node_id_rsa

`tools/release.sh` will perform the following actions when run:

<details>
**a.** Select a GPG key from your private keys. It will use a command similar
MylesBorins marked this conversation as resolved.
Show resolved Hide resolved
to: `gpg --list-secret-keys` to list your keys. If you don't have any keys, it
will bail. If you have only one key, it will use that. If you have more than
Expand Down Expand Up @@ -631,6 +632,7 @@ SHASUMS256.txt.sig.

**g.** Upload the `SHASUMS256.txt` files back to the server into the release
directory.
</details>

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
Expand Down