| 1 |
On Thu, 16 Jun 2016 15:02:13 +0200 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
|
| 4 |
> Hello, everyone. |
| 5 |
> |
| 6 |
> Here's the third bugs.g.o redesign RFC. |
| 7 |
> |
| 8 |
> This time it's about closed bugs. Right now we have two states for |
| 9 |
> them: RESOLVED and VERIFIED. |
| 10 |
> |
| 11 |
> RESOLVED is the usual state that the developers use when they close |
| 12 |
> a bug. It's also the only state that could be directly transferred from |
| 13 |
> other states. |
| 14 |
> |
| 15 |
> VERIFIED is used scarcely, and not really consistently. It can only be |
| 16 |
> used on RESOLVED bugs, and sometimes users use it to confirm that |
| 17 |
> the bug is resolved. |
| 18 |
> |
| 19 |
> To be honest, I don't really see the need for VERIFIED state. Since |
| 20 |
> it's used scarcely, it can't be really relied upon. Some users use it |
| 21 |
> completely incorrectly (e.g. when the bug should be reopened instead). |
| 22 |
|
| 23 |
Since nobody seemed to mind, I've disabled VERIFIED now. I've also |
| 24 |
loosened the workflow so that all (old) VERIFIED bugs can be reopened |
| 25 |
directly. |
| 26 |
|
| 27 |
For stabilization thing, I'm going to wait for more replies/ideas. |
| 28 |
|
| 29 |
-- |
| 30 |
Best regards, |
| 31 |
Michał Górny |
| 32 |
<http://dev.gentoo.org/~mgorny/> |
Archives