djpbessems
/
ContainerImage.Pinniped
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove an unnecessary step from the proposal lifecycle

This commit is contained in:
Ryan Richard 2022-02-17 10:56:13 -08:00
parent 60cc61cdaa
commit 2f7713889a
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
proposals/README.md
View File

@ -186,10 +186,9 @@ implementation PRs.
5. The community critiques the proposal by adding PR reviews in order to mature/converge on the proposal. 5. The community critiques the proposal by adding PR reviews in order to mature/converge on the proposal.
6. When the maintainers reach consensus or supermajority to accept a proposal, they: 6. When the maintainers reach consensus or supermajority to accept a proposal, they:
1. change the status to `accepted`, 1. change the status to `accepted`,
2. adjust the proposal number in the subdirectory's name if needed, 2. record both majority and dissenting opinions,
3. record both majority and dissenting opinions, 3. merge the PR, thus adding the new proposal to the `main` branch,
4. merge the PR, thus adding the new proposal to the `main` branch, 4. code implementation PRs are submitted separately to implement the solution.
5. code implementation PRs are submitted separately to implement the solution.
7. During implementation of an accepted proposal: 7. During implementation of an accepted proposal:
1. if it is discovered that significant unanticipated changes are needed to the proposal, then the implementation 1. if it is discovered that significant unanticipated changes are needed to the proposal, then the implementation
work should be paused and the proposal should be updated with the new details to be reviewed by the maintainers work should be paused and the proposal should be updated with the new details to be reviewed by the maintainers