Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit b50b34b

Browse filesBrowse files
MylesBorinsMylesBorins
committed
doc: put release script specifics in details
Listing all the steps can be confusing an make it seem like the releaser is meant to run each of these steps manually. In fact I personally did that my first release. Let's put those steps in a details block to make it more obvious that it is informational and not steps to follow PR-URL: #35260 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Ruy Adorno <ruyadorno@github.com> Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Michaël Zasso <targos@protonmail.com>
1 parent 1a8f3a8 commit b50b34b
Copy full SHA for b50b34b

File tree

Expand file treeCollapse file tree

1 file changed

+3
-0
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

1 file changed

+3
-0
lines changed
Open diff view settings
Collapse file

‎doc/guides/releases.md‎

Copy file name to clipboardExpand all lines: doc/guides/releases.md
+3Lines changed: 3 additions & 0 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -604,6 +604,8 @@ $ ./tools/release.sh -i ~/.ssh/node_id_rsa
604604

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

607+
<details>
608+
607609
**a.** Select a GPG key from your private keys. It will use a command similar
608610
to: `gpg --list-secret-keys` to list your keys. If you don't have any keys, it
609611
will bail. If you have only one key, it will use that. If you have more than
@@ -637,6 +639,7 @@ SHASUMS256.txt.sig.
637639

638640
**g.** Upload the `SHASUMS256.txt` files back to the server into the release
639641
directory.
642+
</details>
640643

641644
If you didn't wait for ARM builds in the previous step before promoting the
642645
release, you should re-run `tools/release.sh` after the ARM builds have

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.