| 1 |
On Thu, Apr 28, 2011 at 04:07:24PM +0200, 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 |
> CLOSED gone. VERIFIED will be added. |
| 23 |
> |
| 24 |
> So I think we should convert... |
| 25 |
|
| 26 |
+1 |
| 27 |
|
| 28 |
The new workflow makes more sense. |
| 29 |
|
| 30 |
I would mark any new bug as UNCONFIRMED by default, having editbugs |
| 31 |
doesn't ensure your bugs will be confirmed. |
| 32 |
|
| 33 |
|
| 34 |
> -- |
| 35 |
> Regards, |
| 36 |
> Christian Ruppert |
| 37 |
> Role: Gentoo Linux developer, Bugzilla administrator and Infrastructure |
| 38 |
> member |
| 39 |
> Fingerprint: EEB1 C341 7C84 B274 6C59 F243 5EAB 0C62 B427 ABC8 |
| 40 |
|
| 41 |
|
| 42 |
-- |
| 43 |
Alex Alexander | wired |
| 44 |
+ Gentoo Linux Developer |
| 45 |
++ www.linuxized.com |
Archives