An RFC requires tracking issue (#64)

Signed-off-by: tison <[email protected]>
tikv · Apr 23, 2021 · 23d4f9a · 23d4f9a
1 parent 8a82e8f
commit 23d4f9a
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 2 deletions.
diff --git a/README.md b/README.md
@@ -20,8 +20,8 @@ stakeholders can be confident about the direction the project is evolving in.
 
 1. An RFC is submitted as a PR.
 2. Discussion takes place, and the text is revised in response.
-3. The PR is merged or closed when at least two project maintainers reach
-   consensus.
+3. The PR is accepted or rejected when at least two project maintainers reach consensus.
+4. If accepted, create a tracking issue, refer it in the RFC, and finalize by merging.
 
 ## Style of an RFC
 

diff --git a/template.md b/template.md
@@ -1,5 +1,8 @@
 # Title
 
+- RFC PR: https://github.com/tikv/rfcs/pull/0000
+- Tracking Issue: https://github.com/tikv/repo/issues/0000
+
 ## Summary
 
 One para explanation of the proposal.