GeezerVison is showing github.com — doc: add request to hold off publicising sec releases · nodejs/node@11885a7
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: doc/contributing/security-release-process.md +8Lines changed: 8 additions & 0 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -118,6 +118,7 @@ out a better way, forward the email you receive to |
118 | 118 | |
119 | 119 |
|
120 | 120 | * [ ] Create a new issue in [nodejs/tweet][] |
| 121 | + |
121 | 122 | ```text |
122 | 123 | Security release pre-alert: |
123 | 124 |
|
@@ -130,6 +131,13 @@ out a better way, forward the email you receive to |
130 | 131 | https://nodejs.org/en/blog/vulnerability/month-year-security-releases/ |
131 | 132 | ``` |
132 | 133 |
|
| 134 | + We specifically ask that collaborators other than the releasers and security |
| 135 | + steward working on the security release do not tweet or publicise the release |
| 136 | + until the tweet from the Node.js twitter handle goes out. We have often |
| 137 | + seen tweets sent out before the release and associated announcements are |
| 138 | + complete which may confuse those waiting for the release and also takes |
| 139 | + away from the work the releasers have put into shipping the releases. |
| 140 | + |
133 | 141 | * [ ] Request releaser(s) to start integrating the PRs to be released. |
134 | 142 |
|
135 | 143 | * [ ] Notify [docker-node][] of upcoming security release date: _**LINK**_ |
|