This is an automated email from the ASF dual-hosted git repository.
tqchen pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tvm-rfcs.git
The following commit(s) were added to refs/heads/main by this push:
new 6e3b09e Update the guideline of RFC tracking issues (#13)
6e3b09e is described below
commit 6e3b09ec9be3791fc99674b8990ff378fac73f8e
Author: Cody Yu <[email protected]>
AuthorDate: Tue Aug 3 13:36:27 2021 -0700
Update the guideline of RFC tracking issues (#13)
---
README.md | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index 26e6e6b..828769d 100644
--- a/README.md
+++ b/README.md
@@ -83,8 +83,10 @@ the RFC process:
- The formal RFC may link back to the original discussion if there is
additional context or discussion, but all of the final feature design
must be completely described in the pull request.
-- **Tracking Issue**: Upon merging a RFC, a tracking issue will be created in
- the main TVM repository, where implementors can continue sharing
+- **Tracking Issue**: When the RFC review is about to merge, a committer
+ should remind authors to open a tracking issue in the main TVM repository
with the
+ title "[RFC][Tracking][<RFC-no.>] <RFC-title>" and *rfc-tracking* label
+ (added by a committer), where implementors can continue sharing
implementation details (including links to pull requests). The issue will be
closed when the RFC is either completed or postponed.
- **Implementation**: Work will begin on the RFC, with pull requests linking
