From 5e0e01c15edd138f4baf78a003a27da5448a11d8 Mon Sep 17 00:00:00 2001 From: Cody Yu Date: Tue, 27 Jul 2021 10:01:37 -0700 Subject: [PATCH 1/3] Update the guideline of RFC tracking issues Update the guideline of RFC tracking issues --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 26e6e6b3..8233845d 100644 --- a/README.md +++ b/README.md @@ -83,8 +83,9 @@ 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 nearly done and about to merge, + a tracking issue will be created in the main TVM repository with the + *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 From 8d4be1a7fa60553abf9e0cc2191768f20866926b Mon Sep 17 00:00:00 2001 From: Cody Yu Date: Tue, 27 Jul 2021 10:04:56 -0700 Subject: [PATCH 2/3] Update README.md --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 8233845d..1600d8c4 100644 --- a/README.md +++ b/README.md @@ -85,7 +85,8 @@ the RFC process: must be completely described in the pull request. - **Tracking Issue**: When the RFC review is nearly done and about to merge, a tracking issue will be created in the main TVM repository with the - *rfc-tracking* label (added by a committer), where implementors can continue sharing + title "[RFC][Tracking][] " 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 From 4cde53e9c2dc390e02c3e3f6c8cae9b81ae8b3b8 Mon Sep 17 00:00:00 2001 From: Cody Yu Date: Tue, 27 Jul 2021 10:28:05 -0700 Subject: [PATCH 3/3] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 1600d8c4..828769da 100644 --- a/README.md +++ b/README.md @@ -83,8 +83,8 @@ 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**: When the RFC review is nearly done and about to merge, - a tracking issue will be created in the main TVM repository with the +- **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][] " and *rfc-tracking* label (added by a committer), where implementors can continue sharing implementation details (including links to pull requests). The issue will be