From 2f7713889a8082a6e361f6274601785f61494dd0 Mon Sep 17 00:00:00 2001 From: Ryan Richard Date: Thu, 17 Feb 2022 10:56:13 -0800 Subject: [PATCH] Remove an unnecessary step from the proposal lifecycle --- proposals/README.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/proposals/README.md b/proposals/README.md index 346339751..2208774f5 100644 --- a/proposals/README.md +++ b/proposals/README.md @@ -186,10 +186,9 @@ implementation PRs. 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: 1. change the status to `accepted`, - 2. adjust the proposal number in the subdirectory's name if needed, - 3. record both majority and dissenting opinions, - 4. merge the PR, thus adding the new proposal to the `main` branch, - 5. code implementation PRs are submitted separately to implement the solution. + 2. record both majority and dissenting opinions, + 3. merge the PR, thus adding the new proposal to the `main` branch, + 4. code implementation PRs are submitted separately to implement the solution. 7. During implementation of an accepted proposal: 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