| 1 |
So once again: |
| 2 |
|
| 3 |
https://bugs.gentoo.org/docs/en/html/lifecycle.html |
| 4 |
|
| 5 |
*Every* new bug filed by a user without editbugs will have "UNCONFIRMED" |
| 6 |
(old NEW) as fixed status. |
| 7 |
*If* we don't enable the UNCONFIRMED status at all then it will |
| 8 |
CONFIRMED as default but we would enable the UNCONFIRMED status. |
| 9 |
|
| 10 |
Bug wranglers can then assign the bug and they also *can* mark it as |
| 11 |
CONFIRMED *if* they *can* confirm it. |
| 12 |
The maintainer may change the status to IN_PROGRESS (old ASSIGNED) |
| 13 |
afterwards. |
| 14 |
|
| 15 |
The snipped of my first mail may be a bit confusing... It just means: |
| 16 |
NEW will become CONFIRMED, NEW has been fully replaced by CONFIRMED so |
| 17 |
NEW is gone but CONFIRMED is *not* the new default status. CONFIRMED |
| 18 |
would/could be the default for everybody with editbugs. |
| 19 |
ASSIGNED gone, replacement: IN_PROGRESS, |
| 20 |
REOPENED gone, |
| 21 |
CLOSED gone. VERIFIED will be added. |
| 22 |
|
| 23 |
So I think we should convert... |
| 24 |
|
| 25 |
-- |
| 26 |
Regards, |
| 27 |
Christian Ruppert |
| 28 |
Role: Gentoo Linux developer, Bugzilla administrator and Infrastructure |
| 29 |
member |
| 30 |
Fingerprint: EEB1 C341 7C84 B274 6C59 F243 5EAB 0C62 B427 ABC8 |
Archives