Based on the two RFCs I've reviewed, there are two points related to the RFC tracking issue could be improved IMHO.
1. We currently state that the tracking issue should be opened after the RFC PR is merged. However, it means the author needs to file another PR to update the issue link, which seems not necessary to me. As a result, I refined the description, saying that the issue should be opened when the review is nearly done. The reviewer should also remind authors to open a tracking issue and update the link before merging the RFC PR. 2. To better tracking the RFC issues, I created a new label "rfc-tracking". It would be better to add this label to all RFC tracking issues associated with the RFCs proposed here. You can view, comment on, or merge this pull request online at: https://github.com/apache/tvm-rfcs/pull/13 -- Commit Summary -- * Update the guideline of RFC tracking issues -- File Changes -- M README.md (5) -- Patch Links -- https://github.com/apache/tvm-rfcs/pull/13.patch https://github.com/apache/tvm-rfcs/pull/13.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/13
