Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc: simultaneous blog and email of sec announce #31483

Closed
wants to merge 1 commit into from
Closed

doc: simultaneous blog and email of sec announce #31483

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 5 additions & 7 deletions doc/guides/security_release_process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,19 +31,17 @@ the information described.

## Announcement (one week in advance of the planned release)

* Send pre-release announcement to
* [ ] Send pre-release announcement to
https://groups.google.com/forum/#!forum/nodejs-sec.
One of the existing managers can give access (Ben
Noordhuis, Rod Vagg, Michael Dawson). ***LINK TO EMAIL***

* Post pre-release announcement in vulnerabilities section of Nodejs.org blog
(https://github.com/nodejs/nodejs.org/tree/master/locale/en/blog/vulnerability).
* [ ] Post pre-release announcement in vulnerabilities section of Nodejs.org
blog (https://github.com/nodejs/nodejs.org/tree/master/locale/en/blog/vulnerability).
Use last pre-release announcement as a template (it includes blog metadata
such as updates to the banner on the Node.js website to indicate security
releases are coming). Submit PR and leave 1 hour for review. After one hour
even if no reviews, land anyway so that we don't have too big a gap between
post to nodejs-sec and blog. Text was already reviewed in security repo so is
unlikely to attract much additional comment. ***LINK TO BLOG PR AND POST***
releases are coming). Submit PR and land immediately. Text was already
reviewed in security repo. ***LINK TO BLOG PR AND POST***

* [ ] Open an issue in the build working repository with a notification of the
date for the security release. Use this issue to co-ordinate with the build
Expand Down