> 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
I read the release lifecycle a little differently when it comes to the
quality tickets; I don't think it really speaks to those (areas without
known defects but with known skepticism about their stability). If we find
the text to be unclear or not address them we should definitely revise.
Here's wh
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
an
> 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 o
Hi everybody,
Looking at the Dashboard, it seems that the *Quality Testing* tickets are
spread between the Beta and RC releases.
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661
I assumed that those tickets were part of the Beta release but I might have
misunde
> On 9 Dec 2020, at 02:41, Sumanth Pasupuleti
> wrote:
>
> +1 to moving v5-beta changes in trunk to new protocol v6.
>
> Regarding 3.11 and v5, I suppose we could say, v5 could never get matured
> beyond beta, but not sure if it would be confusing to see v6 while v5 is
> still in beta (curio
