ysh329 opened a new issue, #14505:
URL: https://github.com/apache/tvm/issues/14505

   > Although v0.11.0 released on Feb 25 and a relative bugfix minor version 
v0.11.1 released last month, [relative PRs are all the last year 
November](https://github.com/apache/tvm/commits/v0.11.0). This is unhealthy for 
our [RFC-0067 about quarter-based 
releases](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0067-quarterly-releases.md),
 especially for AI infra companies which needs regularly merge with release 
version.
   >
   > Consider v0.11.0 features are from last year Nov and quarter-based 
releases, **I hope at the end of this month we can make a release version**.
   
   In order to continue with our agreed release cycle as per discussion in 
[RFC#67](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0067-quarterly-releases.md)
 , I'd like to propose a schedule for our next TVM release: `v0.12.0`.
   
   This schedule is tentative and may change as we progress through the 
process. In case dates change, this thread will be kept updated.
   
   The proposed schedule is:
   
   - **7 Apr 2023** - a branch `v0.12.0` to be created from `main`
   - **7 Apr 2023** - a tag `v0.12.dev0` to be created, marking the beginning 
of the next development cycle
   - **13 Apr 2023** - cherry-picking soft deadline
     - during this time any reasonable change can be merged, comment on this 
issue with the commit you would like added to the release branch
   - **18 Apr 2023** - cherry-picking **hard deadline**
     - during this time only critical changes will be merged, comment on this 
issue with the commit you would like added to the release branch as well as the 
reasoning for adding it
   - **22 Apr 2023** - Draft release notes published
   - **25 Apr 2023** - release voting opens
   - **28 Apr 2023** - release date
   
   **Note:** for this specific release, given we'll have the end of the year 
period, I've extended the cherry-picking hard deadline in ~3 days, so that we 
some more time to consider patches to be included.
   
   **Call for release managers:** in case you want to be involved in upcoming 
releases, please manifest your interest in this thread and we'll try to 
organise.
   
   See also:
   
   - [Release 
steps](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0067-quarterly-releases.md#reference-level-explanation)
   - [TVM release process 
docs](https://tvm.apache.org/docs/contribute/release_process.html).
   
   cc @apache/tvm-committers [@driazati](https://github.com/driazati) 
[@areusch](https://github.com/areusch) [@Mousius](https://github.com/Mousius) 
[@tqchen](https://github.com/tqchen) 
[@AndrewZhaoLuo](https://github.com/AndrewZhaoLuo)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to