Skip to content

Commit 6dbb212

Browse files
authored
doc: describe ready-for-release state (#844)
* doc: describe ready-for-release state
1 parent cdcb1fc commit 6dbb212

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

Security-Team.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -142,6 +142,9 @@ The expected workflow for issues reported to Node.js is:
142142
getting resolved. Comments on the issue when someone is working on it are
143143
useful, as is assignment of the issue to a person who agrees to be
144144
responsible for following it through to resolution and disclosure.
145+
- Once a fix is ready for release, the issue should be assigned to the
146+
`Ready for release` team, and a comment added indicating the relevant PRs that
147+
need to be merged during the release process.
145148
5. `RESOLVED`: State for an issue that has had a fix published. Issues in this
146149
state should be disclosed.
147150
6. ...: Final states for issues that we will not fix:

0 commit comments

Comments
 (0)