Thanks for bringing this up, this is a major form of confusion right now. I have thought that the fix version is the version which the item will be… fixed in… Others want the fix version to be the version which must not start until the ticket is closed… Both of these opinions are not documented and rely on 1-to-1 conversations… Let's fix this!
Now, for the quality tickets, my understanding is we can not cut a RC release until they are complete, so I “feel” they should be marked beta (which is called out in https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle as Beta is the version under test [1][2]), though I know others feel they should be RC (as we can not cut a RC release until it is complete); which ever stance we take, I hope we document it! 1 - Beta calls out "This release is recommended for test", and the quality tickets are to write and test 2 - RC calls out "If no release-blocking issues are identified within a brief incubation period, release is promoted to GA", so if a quality ticket takes (lets say) 1 month to work on and finds a correctness issue, this may be too late as this could be interpreted as larger than the "brief incubation period", so RC may have been promoted to GA already. On Wed, Dec 9, 2020 at 7:48 AM Michael Semb Wever <m...@apache.org> wrote: > > > Do we want them fixed before we release 4.0-RC or are they part of the > > testing of the RC release? > > > We are so unbearably close, it would be nice to see the beta tickets > narrowed (again) to just the most critical issues. > > Tickets about creating new tests, and bugs edge-case, or not severe or > have an easy-enough workaround, don't need to block a RC release IMHO. Just > like they don't block a patch release when there's other stuff that's > important to roll out. The testing epics tickets too i would think can > continue to roll on during RC. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
