u99127 commented on PR #67: URL: https://github.com/apache/tvm-rfcs/pull/67#issuecomment-1111912140
@driazati - this is a really good starting point for releases and I'm very glad this is coming together. I had a ponder last night. A few additional points to consider for an enhancement to this RFC or make it clearer here in this RFC itself. - Lifecycle of a release , what happens to a release x.y.0 after the release point ? The community has 2 choices, use frugal release manager resources in making sure the next (x.y.0)+1 release happens on schedule and on time . Or continues to improve the quality of x.y.0 by fixing bugs and making sure that x.y.1 / x.y.2 keep happening - but then after a year we'll have too many releases and given where we are in the lifecycle of TVM, this may not be necessary. - At what point do we declare an old release something that the community will not support further ? i.e. x.y.0 is valid for 6 months or a year after which there will be no releases from the branch and the community will not take any bug fixes into the branch ? - Are release managers appointed for the life cycle of a 0.x release - i.e is it the responsibility to keep 0.x until its end of life ? -- 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]
