Skip to content

Commit

Permalink
doc: update instructions for cc
Browse files Browse the repository at this point in the history
- update intructions on adding cc for email to
  nodejs-sec mailing list as UI does not allow it
  to be done directly.

Signed-off-by: Michael Dawson <mdawson@devrus.com>

PR-URL: #39674
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
  • Loading branch information
mhdawson authored and targos committed Aug 24, 2021
1 parent cce95c4 commit c02165d
Showing 1 changed file with 6 additions and 1 deletion.
7 changes: 6 additions & 1 deletion doc/guides/security-release-process.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,6 @@ information described.
* Described in the pre/post announcements
* [ ] Pre-release announcement [email][]: ***LINK TO EMAIL***
* CC: `oss-security@lists.openwall.com`
* Subject: `Node.js security updates for all active release lines, Month Year`
* Body:
```text
Expand All @@ -52,6 +51,12 @@ information described.
```
(Get access from existing manager: Ben Noordhuis, Rod Vagg, Michael Dawson)

* [ ] CC `oss-security@lists.openwall.com` on pre-release

The google groups UI does not support adding a CC, until we figure
out a better way, forward the email you receive to
`oss-security@lists.openwall.com` as a CC.

* [ ] Pre-release announcement to nodejs.org blog: ***LINK TO BLOG***
(Re-PR the pre-approved branch from nodejs-private/nodejs.org-private to
nodejs/nodejs.org)
Expand Down

0 comments on commit c02165d

Please sign in to comment.