u99127 commented on PR #67: URL: https://github.com/apache/tvm-rfcs/pull/67#issuecomment-1124315894
> I think the main outstanding thing is the question of support here. I'd love for a few more folks to weigh in, tagging a few folks who may have ideas: @tqchen @jroesch @kparzysz-quic @u99127 @Mousius @leandron @comaniac @zhiics @Hzfengsy @ZihengJiang @yzhliu @masahi @icemelon > > broadly, the question is: once we release version `0.X.0`, should we discover a bug, we should likely fix it on that branch and on `main` and release `0.X.Y`. how long shall we commit to doing that? If a bug is discovered on `0.X-1.0`, will we fix it? > > my vote is the following (for now, we can revisit at 1.0): > > * we agree we will fix major bugs on `0.X.Y` where `0.X.Y` is the latest release. Ack. > * when we make a new minor version release e.g. `0.(X+1).0`, we will stop maintaining releases starting with `0.X.` at that time. When we make a new minor version release 0.(x+1).0 , we do a 0.X.(Y+1) and close the branch, otherwise there might be bug fixes since 0.x.y that never see a release or the light of day. I'd take it with that minor adjustments. > * committers/pmcs should exercise their judgement when determining if something warrants a fix. s/fix/backport > * the same policy should apply on the forum--if someone asks a question on an old minor release version, it should be acceptable to ask them to reproduce it on the latest release. Hmm, I'd suggest that we say all bugs / questions should be reproduced with trunk / main and the latest release rather than an unsupported release. We probably need to update the "Releases tab" on gh to make this work. This is looking like good small steps forward. Very good to see this coming together. Ramana -- 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]
