diff options
author | Rich Trott <rtrott@gmail.com> | 2020-09-11 15:50:33 +0300 |
---|---|---|
committer | Rich Trott <rtrott@gmail.com> | 2020-09-14 02:06:19 +0300 |
commit | b5715d2283786bf2d6d6cc529bd3f8d1f122982a (patch) | |
tree | 4c1b0a93adb5bd586e8c20fc390b417df74c149f | |
parent | 692910dd304644f63d2576d2476c4dca3e33799f (diff) |
doc: perform cleanup on security-release-process.md
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>
-rw-r--r-- | doc/guides/security-release-process.md | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/guides/security-release-process.md b/doc/guides/security-release-process.md index 2ae3da0613c..0ada9b63742 100644 --- a/doc/guides/security-release-process.md +++ b/doc/guides/security-release-process.md @@ -1,8 +1,8 @@ -# Security Release Process +# Security release process 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, 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 information described. @@ -17,7 +17,7 @@ information described. * ... * [ ] 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.) * [ ] pre-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 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. - 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. @@ -69,9 +69,9 @@ information described. * (Re-PR the pre-approved branch from nodejs-private/nodejs.org-private to 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. - 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. 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 [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 +[nodejs/build]: https://github.com/nodejs/build/issues |