| 1 |
On Thursday 28 of April 2011 16:07:24 Christian Ruppert wrote: |
| 2 |
> So once again: |
| 3 |
> |
| 4 |
> https://bugs.gentoo.org/docs/en/html/lifecycle.html |
| 5 |
> |
| 6 |
> *Every* new bug filed by a user without editbugs will have "UNCONFIRMED" |
| 7 |
> (old NEW) as fixed status. |
| 8 |
> *If* we don't enable the UNCONFIRMED status at all then it will |
| 9 |
> CONFIRMED as default but we would enable the UNCONFIRMED status. |
| 10 |
> |
| 11 |
> Bug wranglers can then assign the bug and they also *can* mark it as |
| 12 |
> CONFIRMED *if* they *can* confirm it. |
| 13 |
> The maintainer may change the status to IN_PROGRESS (old ASSIGNED) |
| 14 |
> afterwards. |
| 15 |
> |
| 16 |
> The snipped of my first mail may be a bit confusing... It just means: |
| 17 |
> NEW will become CONFIRMED, NEW has been fully replaced by CONFIRMED so |
| 18 |
> NEW is gone but CONFIRMED is *not* the new default status. CONFIRMED |
| 19 |
> would/could be the default for everybody with editbugs. |
| 20 |
> ASSIGNED gone, replacement: IN_PROGRESS, |
| 21 |
> REOPENED gone, |
| 22 |
|
| 23 |
+1 (with comment, see below) |
| 24 |
|
| 25 |
It makes a lot more sense (and it's free from enterprisey meaning wrt ASSIGNED |
| 26 |
and such) |
| 27 |
|
| 28 |
I'd leave the default resolution status for newly created bug as UNCONFIRMED |
| 29 |
also for editbugs-accounts. It's not that it cannot be changed to CONFIRMED in |
| 30 |
'new bug' extended form. |
| 31 |
|
| 32 |
> CLOSED gone. VERIFIED will be added. |
| 33 |
|
| 34 |
I have a little worry thought (that may have been addressed somewhere in this |
| 35 |
thread) - why is VERIFIED being added? To me it's not needed at all and there |
| 36 |
are people who seem to have the same opinion: |
| 37 |
|
| 38 |
http://www.mail-archive.com/gentoo-dev@l.g.o/msg39023.html |
| 39 |
|
| 40 |
-- |
| 41 |
regards |
| 42 |
MM |
Archives