On Fr, 2020-12-04 at 07:42 +0300, NIkolai Marchenko wrote:
> Let's be honest with your users:
> P0: almost sure to block a release.
> P1: We will act on it if the maintainer is in the mood some day when it's
> still fresh
> P2: We will fix it, maybe
> P3: thank you for informing us.
Funny, this
> From: Development On Behalf Of NIkolai
> Marchenko
> Sent: Friday, December 4, 2020 9:45 AM
> Subject: Re: [Development] Long-lived P1 issues
>
>> Currently, there are 1175 open P1 issues in the QTBUG project. 583 of those
>> issues had that priority set more th
> -Original Message-
> From: Development On Behalf Of
> Jason McDonald
> Sent: Friday, 4 December 2020 5:25 AM
> To: Kai Köhne
> Cc: development@qt-project.org
> Subject: Re: [Development] Long-lived P1 issues
>
>
> On Fri, 4 Dec 2020 at 02:09, Kai K
> Currently, there are 1175 open P1 issues in the QTBUG project. 583 of
those issues had that priority set more than one year ago,
I am not saying no one ever fixes those, but given the premise of this
thread. The "promise" of every PX description is certainly broken enough
_in general_ that my r
On 12/4/20 5:42 AM, NIkolai Marchenko wrote:
Let's be honest with your users:
P0: almost sure to block a release.
P1: We will act on it if the maintainer is in the mood some day when
it's still fresh
P2: We will fix it, maybe
P3: thank you for informing us.
That's neither helpful nor true. I
Let's be honest with your users:
P0: almost sure to block a release.
P1: We will act on it if the maintainer is in the mood some day when it's
still fresh
P2: We will fix it, maybe
P3: thank you for informing us.
> I suggest to simplify P3, P4 descriptions though to
>>
>> P2: Important, should
On Fri, 4 Dec 2020 at 02:09, Kai Köhne wrote:
> > Was there any outcome from this discussion? Like, re-evaluating priority
> > levels and what they mean in terms of release blockers?
>
I note that the number of open P1's has dropped from 1175 to 1063. Some of
that decline has been from genuine
> -Original Message-
>[...]
> > (Clicking the ? button next to the priority field in Jira shows the
> > following definition for P1: "Urgent and Important, will STOP the
> > release if matched with set FixVersion field. This includes
> > regressions from the last version that are not edge c
Hi,
Il 03/11/20 05:34, Jason McDonald ha scritto:
Currently, there are 1175 open P1 issues in the QTBUG project. 583 of
those issues had that priority set more than one year ago, 342 of those
had their priority set more than two years ago, and 175 of those more
than three years ago.
If an i
> ... resulting in users complaining about "high priority bugs get ignored".
They're still complaining? Impressive. I have already passed the phase of
resignation and
just wonder why there is still a public bug tracker.
--
Best Regards,
Bernhard Lindner
On Tue, Nov 03, 2020 at 10:34:29AM +, Alex Blasche wrote:
After all the trinity of quality - time - resources must be adhered to.
indeed, but you're still failing to draw the obvious conclusion. ;)
"priority inflation" is a "natural" effect of an issue tracker drowning
in unresolved issue
> On Nov 3, 2020, at 12:56, Eike Ziller wrote:
>
>
>
>> On Nov 3, 2020, at 11:34, Alex Blasche wrote:
>>
>>
>>
>>> -Original Message-
>>> From: Development On Behalf Of
>>> Jason McDonald
>>
>>> Looking at the huge list of P1s we have right now, I have absolutely no idea
>>> wha
On 3 Nov 2020, at 12:56, Eike Ziller
mailto:eike.zil...@qt.io>> wrote:
It is something that we interpret into a combination of two separated fields in
JIRA, with the meaning of Fix Version even having dual meaning depending on the
“Resolution” state of a task
Maybe we should have two fix ver
> On Nov 3, 2020, at 11:34, Alex Blasche wrote:
>
>
>
>> -Original Message-
>> From: Development On Behalf Of
>> Jason McDonald
>
>> Looking at the huge list of P1s we have right now, I have absolutely no idea
>> what issues are genuinely blocking Qt 6.0 or if there are any that I c
> -Original Message-
> From: Development On Behalf Of
> Jason McDonald
> Looking at the huge list of P1s we have right now, I have absolutely no idea
> what issues are genuinely blocking Qt 6.0 or if there are any that I could
> help out
> with. I could spend literally weeks just readi
On Tue, 3 Nov 2020 at 18:48, Eike Ziller wrote:
> I disagree, especially if the fix version is a planning tool for the
> individual developer.
> The point is that you still at least need the rough categories of
>
> 1. must be handled _immediately_ (build breakage “P0”)
> 2. release management dec
On Tue, 3 Nov 2020 at 18:39, Allan Sandfeld Jensen wrote:
> On Dienstag, 3. November 2020 05:34:02 CET Jason McDonald wrote:
> > If an issue is not important enough to get attention within a year, is it
> > really P1?
>
> But how many of those are accepted? P1 is just set on the assumption the
>
> On Nov 3, 2020, at 09:07, Ulf Hermann wrote:
>
>> Currently, there are 1175 open P1 issues in the QTBUG project. 583 of those
>> issues had that priority set more than one year ago, 342 of those had their
>> priority set more than two years ago, and 175 of those more than three years
>> a
Il 03/11/20 05:34, Jason McDonald ha scritto:
Currently, there are 1175 open P1 issues in the QTBUG project. 583 of
those issues had that priority set more than one year ago, 342 of those
had their priority set more than two years ago, and 175 of those more
than three years ago.
If an issue
On Dienstag, 3. November 2020 05:34:02 CET Jason McDonald wrote:
> Some food for thought for module maintainers.
>
> Currently, there are 1175 open P1 issues in the QTBUG project. 583 of
> those issues had that priority set more than one year ago, 342 of those had
> their priority set more th
> On 3 Nov 2020, at 09:07, Ulf Hermann wrote:
>
>> Currently, there are 1175 open P1 issues in the QTBUG project. 583 of those
>> issues had that priority set more than one year ago, 342 of those had their
>> priority set more than two years ago, and 175 of those more than three years
>> ago
Currently, there are 1175 open P1 issues in the QTBUG project. 583 of
those issues had that priority set more than one year ago, 342 of those
had their priority set more than two years ago, and 175 of those more
than three years ago.
Let's be honest about this: The priority field is meaningle
Some food for thought for module maintainers.
Currently, there are 1175 open P1 issues in the QTBUG project. 583 of
those issues had that priority set more than one year ago, 342 of those had
their priority set more than two years ago, and 175 of those more than
three years ago.
If an issue
23 matches
Mail list logo
