From 8b72e8627be34c5a545871322158e4fe94214cf0 Mon Sep 17 00:00:00 2001 From: teor Date: Mon, 10 May 2021 23:17:42 +1000 Subject: [PATCH] Make the RFC TOC into a separate step (#2126) We might remember it better that way. --- CONTRIBUTING.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 91c45102..4678a3d8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -74,9 +74,10 @@ with the PR number. 8. When the RFC is merged, take the next available RFC number (not conflicting with any existing RFCs or design PRs) and name the RFC file accordingly, e.g., -`0027-my-feature.md` for number 27. Make sure that `book/src/SUMMARY.md` links -to the numbered RFC. +`0027-my-feature.md` for number 27. -7. After the RFC is accepted, create an issue for the implementation of the +9. Make sure that `book/src/SUMMARY.md` links to the new number for the RFC. + +10. After the RFC is accepted, create an issue for the implementation of the design, and update the RFC header and PR description with the implementation issue number.