> 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…
David, my understanding of it doesn't quite fit into this… Issues with a fixVersion of 4.0-beta indicate they are a blocker to the first RC release. Issues with a fixVersion of 4.0-rc indicate they are a blocker to the GA release. Issues with a fixVersion of 4.0.x indicate they are not blocking GA, but should be fixed in some subsequent patch version. At the same time, of course no one is preventing 4.0-rc and 4.0.x issues from going into a 4.0-betaX release. https://lists.apache.org/thread.html/r734c071b9f921f9e07455d4fe2262703c8f4daeddd9065a28a4cc4ed%40%3Cdev.cassandra.apache.org%3E > If there are no known bugs to be fixed before release, we promote to RC. It would be really helpful to elaborate on this, because there are always known bugs in every system. And if we are then to say "blocking bugs" what do we then mean by that? There are plenty of bugs that can be assigned fixVersion 4.0.x And this thinking extends to the testing epics too. There's this fuzzy line of knowing when those epics have done enough to discover those blocking bugs, or shall we continue with the testing epics forever to find the non-blocking bugs…
