Commit 953f2e9
doc: add nodejs/tweet issue creation to sec. doc
This commit adds a suggestion to create a github issue for the security
release tweets. Currently, the security release document requests that
these tweets be created by asking in the #nodejs-social channel. Someone
from that channel would then create an issue, so we could just create
the issue ourselves.
PR-URL: #39940
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>1 parent 2343c39 commit 953f2e9
1 file changed
Lines changed: 19 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -64,10 +64,18 @@ out a better way, forward the email you receive to | |||
| 64 | 64 | (Re-PR the pre-approved branch from nodejs-private/nodejs.org-private to | |
| 65 | 65 | nodejs/nodejs.org) | |
| 66 | 66 | ||
| 67 | - * [ ] Post in the #nodejs-social channel in the OpenJS Foundation Slack | ||
| 68 | - asking that the social team tweet/retweet the pre-announcement. | ||
| 69 | - If you are on Twitter, you can just direct message the `@nodejs` handle. | ||
| 67 | + * [ ] Create a new issue in [nodejs/tweet][] | ||
| 68 | + ```text | ||
| 69 | + Security release pre-alert: | ||
| 70 | + | ||
| 71 | + We will release new versions of <add versions> release lines on or shortly | ||
| 72 | + after Day Month Date, Year in order to address: | ||
| 70 | 73 | ||
| 74 | + - # high severity issues | ||
| 75 | + - # moderate severity issues | ||
| 76 | + | ||
| 77 | + https://nodejs.org/en/blog/vulnerability/month-year-security-releases/ | ||
| 78 | + ``` | ||
| 71 | 79 | * [ ] Request releaser(s) to start integrating the PRs to be released. | |
| 72 | 80 | ||
| 73 | 81 | * [ ] Notify [docker-node][] of upcoming security release date: ***LINK*** | |
@@ -106,10 +114,14 @@ out a better way, forward the email you receive to | |||
| 106 | 114 | * (Re-PR the pre-approved branch from nodejs-private/nodejs.org-private to | |
| 107 | 115 | nodejs/nodejs.org) | |
| 108 | 116 | ||
| 109 | - * [ ] Post in the #nodejs-social channel in the OpenJS Foundation Slack | ||
| 110 | - asking that the social team tweet/retweet the announcement. | ||
| 111 | - If you are on Twitter, you can just direct message the `@nodejs` handle. | ||
| 117 | + * [ ] Create a new issue in [nodejs/tweet][] | ||
| 118 | + ```text | ||
| 119 | + Security release: | ||
| 120 | + | ||
| 121 | + New security releases are now available for versions <add versions> of Node.js. | ||
| 112 | 122 | ||
| 123 | + https://nodejs.org/en/blog/vulnerability/month-year-security-releases/ | ||
| 124 | + ``` | ||
| 113 | 125 | * [ ] Comment in [docker-node][] issue that release is ready for integration. | |
| 114 | 126 | The docker-node team will build and release docker image updates. | |
| 115 | 127 | ||
@@ -136,3 +148,4 @@ out a better way, forward the email you receive to | |||
| 136 | 148 | [docker-node]: https://github.com/nodejs/docker-node/issues | |
| 137 | 149 | [email]: https://groups.google.com/forum/#!forum/nodejs-sec | |
| 138 | 150 | [nodejs/build]: https://github.com/nodejs/build/issues | |
| 151 | + [nodejs/tweet]: https://github.com/nodejs/tweet/issues | ||
0 commit comments