Commit 8b5339d
doc: rename README section for Release Keys
The section of the README currently labeled "Release Team" isn't about
the team much and is very much about the keys. Rename it "Release Keys"
so that it's purpose matches it's name.
PR-URL: #23927
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Matheus Marchini <mat@mmarchini.me>1 parent 6768751 commit 8b5339d
1 file changed
Lines changed: 7 additions & 7 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -31,7 +31,7 @@ The Node.js project uses an [open governance model](./GOVERNANCE.md). The | |||
| 31 | 31 | * [Current Project Team Members](#current-project-team-members) | |
| 32 | 32 | * [TSC (Technical Steering Committee)](#tsc-technical-steering-committee) | |
| 33 | 33 | * [Collaborators](#collaborators) | |
| 34 | - * [Release Team](#release-team) | ||
| 34 | + * [Release Keys](#release-keys) | ||
| 35 | 35 | * [Contributing to Node.js](#contributing-to-nodejs) | |
| 36 | 36 | ||
| 37 | 37 | ## Support | |
@@ -81,7 +81,7 @@ your expectations. | |||
| 81 | 81 | changes. Use with caution. | |
| 82 | 82 | ||
| 83 | 83 | Current and LTS releases follow [Semantic Versioning](https://semver.org). A | |
| 84 | - member of the [Release Team](#release-team) signs each Current and LTS release. | ||
| 84 | + member of the Release Team [signs](#release-keys) each Current and LTS release. | ||
| 85 | 85 | For more information, see the | |
| 86 | 86 | [Release README](https://github.com/nodejs/Release). | |
| 87 | 87 | ||
@@ -133,9 +133,9 @@ $ grep node-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c - | |||
| 133 | 133 | ||
| 134 | 134 | For Current and LTS, the GPG detached signature of `SHASUMS256.txt` is in | |
| 135 | 135 | `SHASUMS256.txt.sig`. You can use it with `gpg` to verify the integrity of | |
| 136 | - `SHASUM256.txt`. You will first need to import all the GPG keys of individuals | ||
| 137 | - authorized to create releases. They are at the bottom of this README under | ||
| 138 | - [Release Team](#release-team). To import the keys: | ||
| 136 | + `SHASUM256.txt`. You will first need to import | ||
| 137 | + [the GPG keys of individuals authorized to create releases](#release-keys). To | ||
| 138 | + import the keys: | ||
| 139 | 139 | ||
| 140 | 140 | ```console | |
| 141 | 141 | $ gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D | |
@@ -555,9 +555,9 @@ For information about the governance of the Node.js project, see | |||
| 555 | 555 | Collaborators follow the [COLLABORATOR_GUIDE.md](./COLLABORATOR_GUIDE.md) in | |
| 556 | 556 | maintaining the Node.js project. | |
| 557 | 557 | ||
| 558 | - ### Release Team | ||
| 558 | + ### Release Keys | ||
| 559 | 559 | ||
| 560 | - Node.js releases are signed with one of the following GPG keys: | ||
| 560 | + GPG keys used to sign Node.js releases: | ||
| 561 | 561 | ||
| 562 | 562 | * **Colin Ihrig** <cjihrig@gmail.com> | |
| 563 | 563 | `94AE36675C464D64BAFA68DD7434390BDBE9B9C5` | |
0 commit comments