Skip to content

Update the guideline of RFC tracking issues #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tqchen merged 3 commits into from
Aug 3, 2021
Merged

Update the guideline of RFC tracking issues #13

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5e0e01c
Update the guideline of RFC tracking issues
comaniac Jul 27, 2021
8d4be1a
Update README.md
comaniac Jul 27, 2021
4cde53e
Update README.md
comaniac Jul 27, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down