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

doc: perform cleanup on security-release-process.md

Browse Source 
These are exceedingly minor, but I'm doing them anyway for consistency
across our docs (whether internal process docs or user-facing docs).

* ASCII order for references
* Minor punctuation adjustments
* Use product capitalization for Twitter and Slack
* Sentence-case for header

PR-URL: https://github.com/nodejs/node/pull/35154
Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
This commit is contained in:
Rich Trott 2020-09-11 05:50:33 -07:00
parent 692910dd30
commit b5715d2283
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/guides/security-release-process.md
View File

@ -1,8 +1,8 @@
# Security Release Process # Security release process
The security release process covers the steps required to plan/implement a The security release process covers the steps required to plan/implement a
security release. This document is copied into the description of the Next security release. This document is copied into the description of the Next
Security Release, and used to track progress on the release. It contains ***TEXT Security Release and used to track progress on the release. It contains ***TEXT
LIKE THIS*** which will be replaced during the release process with the LIKE THIS*** which will be replaced during the release process with the
information described. information described.
@ -17,7 +17,7 @@ information described.
* ... * ...
* [ ] PR release announcements in [private](https://github.com/nodejs-private/nodejs.org-private): * [ ] PR release announcements in [private](https://github.com/nodejs-private/nodejs.org-private):
* (Use previous PRs as templates, don't forget to update the site banner, and * (Use previous PRs as templates. Don't forget to update the site banner and
the date in the slug so that it will move to the top of the blog list.) the date in the slug so that it will move to the top of the blog list.)
* [ ] pre-release: ***LINK TO PR*** * [ ] pre-release: ***LINK TO PR***
* [ ] post-release: ***LINK TO PR*** * [ ] post-release: ***LINK TO PR***
@ -44,9 +44,9 @@ information described.
(Re-PR the pre-approved branch from nodejs-private/nodejs.org-private to (Re-PR the pre-approved branch from nodejs-private/nodejs.org-private to
nodejs/nodejs.org) nodejs/nodejs.org)
* [ ] Post in the #nodejs-social channel in the OpenJS Foundation slack * [ ] Post in the #nodejs-social channel in the OpenJS Foundation Slack
asking that the social team tweet/retweet the pre-announcement. asking that the social team tweet/retweet the pre-announcement.
If you are on twitter you can just direct message the `@nodejs` handle. If you are on Twitter, you can just direct message the `@nodejs` handle.
* [ ] Request releaser(s) to start integrating the PRs to be released. * [ ] Request releaser(s) to start integrating the PRs to be released.
@ -69,9 +69,9 @@ information described.
* (Re-PR the pre-approved branch from nodejs-private/nodejs.org-private to * (Re-PR the pre-approved branch from nodejs-private/nodejs.org-private to
nodejs/nodejs.org) nodejs/nodejs.org)
* [ ] Post in the #nodejs-social channel in the OpenJS Foundation slack * [ ] Post in the #nodejs-social channel in the OpenJS Foundation Slack
asking that the social team tweet/retweet the announcement. asking that the social team tweet/retweet the announcement.
If you are on twitter you can just direct message the `@nodejs` handle. If you are on Twitter, you can just direct message the `@nodejs` handle.
* [ ] Comment in [docker-node][] issue that release is ready for integration. * [ ] Comment in [docker-node][] issue that release is ready for integration.
The docker-node team will build and release docker image updates. The docker-node team will build and release docker image updates.
@ -93,5 +93,5 @@ information described.
[H1 CVE requests]: https://hackerone.com/nodejs/cve_requests [H1 CVE requests]: https://hackerone.com/nodejs/cve_requests
[docker-node]: https://github.com/nodejs/docker-node/issues [docker-node]: https://github.com/nodejs/docker-node/issues
[nodejs/build]: https://github.com/nodejs/build/issues
[email]: https://groups.google.com/forum/#!forum/nodejs-sec [email]: https://groups.google.com/forum/#!forum/nodejs-sec
[nodejs/build]: https://github.com/nodejs/build/issues