Hi,
I'd like to propose replacing the current UNCONFIRMED and CONFIRMED bug
states with a simple NEW state. Why?
1. Only a handful of developers actually uses these two statuses
in a meaningful way.
2. Some users are confused and demotivated by having their bugs stay
UNCONFIRMED for a long time
> On 3 Dec 2022, at 07:09, Michał Górny wrote:
>
> Hi,
>
> I'd like to propose replacing the current UNCONFIRMED and CONFIRMED bug
> states with a simple NEW state. Why?
>
> 1. Only a handful of developers actually uses these two statuses
> in a meaningful way.
>
> 2. Some users are confuse
> On Sat, 03 Dec 2022, Michał Górny wrote:
> I'd like to propose replacing the current UNCONFIRMED and CONFIRMED
> bug states with a simple NEW state. Why?
> 1. Only a handful of developers actually uses these two statuses
> in a meaningful way.
> 2. Some users are confused and demotivated b
On Sat, 2022-12-03 at 09:39 +0100, Ulrich Mueller wrote:
> > > > > > On Sat, 03 Dec 2022, Michał Górny wrote:
>
> > I'd like to propose replacing the current UNCONFIRMED and CONFIRMED
> > bug states with a simple NEW state. Why?
>
> > 1. Only a handful of developers actually uses these two status
On 12/3/22 10:53, Michał Górny wrote:
On Sat, 2022-12-03 at 09:39 +0100, Ulrich Mueller wrote:
Then rename UNCONFIRMED to NEW-WITH-SUGAR-ON-TOP-WE-ARE-A-HAPPY-
COMMUNITY,
Done.
I do search for bugs using pybugz and gre3p for CONFIRMED and do wonder
if/when I shall grep for NEW too ?
--
On 03/12/2022 08.09, Michał Górny wrote:
Hi,
I'd like to propose replacing the current UNCONFIRMED and CONFIRMED bug
states with a simple NEW state. Why?
1. Only a handful of developers actually uses these two statuses
in a meaningful way.
2. Some users are confused and demotivated by having
On Sat, 2022-12-03 at 11:42 +0100, Florian Schmaus wrote:
> On 03/12/2022 08.09, Michał Górny wrote:
> > Hi,
> >
> > I'd like to propose replacing the current UNCONFIRMED and CONFIRMED bug
> > states with a simple NEW state. Why?
> >
> > 1. Only a handful of developers actually uses these two st
> On Sat, 03 Dec 2022, Michał Górny wrote:
>> > I'd like to propose replacing the current UNCONFIRMED and CONFIRMED
>> > bug states with a simple NEW state. Why?
>>
>> > 1. Only a handful of developers actually uses these two statuses
>> > in a meaningful way.
>>
>> > 2. Some users are confu
On 03/12/2022 12.34, Michał Górny wrote:
On Sat, 2022-12-03 at 11:42 +0100, Florian Schmaus wrote:
On 03/12/2022 08.09, Michał Górny wrote:
Hi,
I'd like to propose replacing the current UNCONFIRMED and CONFIRMED bug
states with a simple NEW state. Why?
1. Only a handful of developers actuall
> On Sat, 03 Dec 2022, Ulrich Mueller wrote:
> Some people found that not satisfactory, so NEW and ASSIGNED were
> replaced by CONFIRMED and IN_PROGRESS. (We also had status REOPENED
> which was removed with the same change.) Unfortunately, I cannot find
> the old discussion, but [1] suggests
On Sat, 2022-12-03 at 13:10 +0100, Florian Schmaus wrote:
> On 03/12/2022 12.34, Michał Górny wrote:
> > On Sat, 2022-12-03 at 11:42 +0100, Florian Schmaus wrote:
> > > On 03/12/2022 08.09, Michał Górny wrote:
> > > > Hi,
> > > >
> > > > I'd like to propose replacing the current UNCONFIRMED and CO
On 03/12/2022 13.20, Michał Górny wrote:
On Sat, 2022-12-03 at 13:10 +0100, Florian Schmaus wrote:
On 03/12/2022 12.34, Michał Górny wrote:
On Sat, 2022-12-03 at 11:42 +0100, Florian Schmaus wrote:
On 03/12/2022 08.09, Michał Górny wrote:
Hi,
I'd like to propose replacing the current UNCONFI
On Sat, 2022-12-03 at 14:45 +0100, Florian Schmaus wrote:
> I think having UNCONFIRMED / CONFIRMED *helps* the issue reporter, and
> other (affected) persons, to decide if they need to "chase" the issue's
> assigned entity.
>
> Assume looking at the open bugs list of a developer. If the develope
On 03/12/2022 14.50, Michał Górny wrote:
On Sat, 2022-12-03 at 14:45 +0100, Florian Schmaus wrote:
I think having UNCONFIRMED / CONFIRMED *helps* the issue reporter, and
other (affected) persons, to decide if they need to "chase" the issue's
assigned entity.
Assume looking at the open bugs list
On 12/3/22 08:59, Florian Schmaus wrote:
On 03/12/2022 14.50, Michał Górny wrote:
On Sat, 2022-12-03 at 14:45 +0100, Florian Schmaus wrote:
I think having UNCONFIRMED / CONFIRMED *helps* the issue reporter, and
other (affected) persons, to decide if they need to "chase" the issue's
assigned
Hi all,
I'd like to propose replacing the current UNCONFIRMED and CONFIRMED bug
states with a simple NEW state. Why?
1. Only a handful of developers actually uses these two statuses
in a meaningful way.
2. Some users are confused and demotivated by having their bugs stay
UNCONFIRMED for a lon
On Sat, Dec 3, 2022 at 2:09 AM Michał Górny wrote:
>
> Hi,
>
> I'd like to propose replacing the current UNCONFIRMED and CONFIRMED bug
> states with a simple NEW state. Why?
>
> 1. Only a handful of developers actually uses these two statuses
> in a meaningful way.
>
> 2. Some users are confused
17 matches
Mail list logo