1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: rename README section for Release Keys

Browse Source 
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: https://github.com/nodejs/node/pull/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>
This commit is contained in:
Rich Trott 2018-10-27 12:37:12 -07:00
parent 97d9ccdeb8
commit d7b95f1fe4
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -31,7 +31,7 @@ The Node.js project uses an [open governance model](./GOVERNANCE.md). The
* [Current Project Team Members](#current-project-team-members) * [Current Project Team Members](#current-project-team-members)
* [TSC (Technical Steering Committee)](#tsc-technical-steering-committee) * [TSC (Technical Steering Committee)](#tsc-technical-steering-committee)
* [Collaborators](#collaborators) * [Collaborators](#collaborators)
* [Release Team](#release-team) * [Release Keys](#release-keys)
* [Contributing to Node.js](#contributing-to-nodejs) * [Contributing to Node.js](#contributing-to-nodejs)
## Support ## Support
@ -81,7 +81,7 @@ your expectations.
changes. Use with caution. changes. Use with caution.
Current and LTS releases follow [Semantic Versioning](https://semver.org). A Current and LTS releases follow [Semantic Versioning](https://semver.org). A
member of the [Release Team](#release-team) signs each Current and LTS release. member of the Release Team [signs](#release-keys) each Current and LTS release.
For more information, see the For more information, see the
[Release README](https://github.com/nodejs/Release). [Release README](https://github.com/nodejs/Release).
@ -133,9 +133,9 @@ $ grep node-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c -
For Current and LTS, the GPG detached signature of `SHASUMS256.txt` is in For Current and LTS, the GPG detached signature of `SHASUMS256.txt` is in
`SHASUMS256.txt.sig`. You can use it with `gpg` to verify the integrity of `SHASUMS256.txt.sig`. You can use it with `gpg` to verify the integrity of
`SHASUM256.txt`. You will first need to import all the GPG keys of individuals `SHASUM256.txt`. You will first need to import
authorized to create releases. They are at the bottom of this README under [the GPG keys of individuals authorized to create releases](#release-keys). To
[Release Team](#release-team). To import the keys: import the keys:
```console ```console
$ gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D $ gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D
@ -555,9 +555,9 @@ For information about the governance of the Node.js project, see
Collaborators follow the [COLLABORATOR_GUIDE.md](./COLLABORATOR_GUIDE.md) in Collaborators follow the [COLLABORATOR_GUIDE.md](./COLLABORATOR_GUIDE.md) in
maintaining the Node.js project. maintaining the Node.js project.
### Release Team ### Release Keys
Node.js releases are signed with one of the following GPG keys: GPG keys used to sign Node.js releases:
* **Colin Ihrig** &lt;cjihrig@gmail.com&gt; * **Colin Ihrig** &lt;cjihrig@gmail.com&gt;
`94AE36675C464D64BAFA68DD7434390BDBE9B9C5` `94AE36675C464D64BAFA68DD7434390BDBE9B9C5`