tqchen commented on code in PR #67: URL: https://github.com/apache/tvm-rfcs/pull/67#discussion_r857561642
########## 0067-quarterly-releases.md: ########## @@ -0,0 +1,53 @@ +- Feature Name: Release Schedule +- Start Date: 2022-04-21 +- RFC PR: [apache/tvm-rfcs#67](https://github.com/apache/tvm-rfcs/pull/67) + +# Summary +This RFC proposes that TVM move to a quarterly release schedule. Releases would happen every 3 months or so on a schedule set well in advance, independent of individual feature development in TVM. + +# Motivation +Releases are essential to the usage of TVM, especially now that are beginning to work on publishing binary packages for TVM under PyPi. Making TVM releases frequent forces the release process to become well documented and simple rather than bespoke and only achievable by a small group. Users benefit from releases by seeing that the the project is still under active development and providing an easy way to get new features. As of this RFC it has been five months since the last release. It could easily confuse new users when they expect some TVM feature that was only developed recently but is not present in the latest official release. + + +# Guide-level explanation +TVM has [release process documentation](https://tvm.apache.org/docs/contribute/release_process.html). This RFC proposes that the release candidate vote thread be abolished in favor of a mechanical schedule where releases happen roughly every three months. A release branch will be cut, evaluated for a period of two weeks, then a release published. Publishing a release entails: Review Comment: Thanks @driazati for proposing the change and bringing up the goal of making release streamlined (which we all share). Just to clarify this particular point(of release voting) as it is something that is related to the policy. Overall release policy is something that apache handles (extra) carefully. Release voting thread is mandatory per policy and it is not something that we can change project-wide. The rationale is that the release voting thread brings broad community awareness and overall license requirements. A release needs at least three PMC vote to be shipped. We can however, keep the schedule streamlined and improve the overall efficiency driven by a release manager. The original release policy guide is a good reference pt -- about the GPG key needs and where to upload, posts. -- 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]
