| 1 |
On Fri, Jun 17, 2016 at 9:02 AM, Kristian Fiskerstrand <k_f@g.o> wrote: |
| 2 |
> On 06/17/2016 02:18 PM, Rich Freeman wrote: |
| 3 |
> |
| 4 |
>> If I'm a maintainer and I resolve a bug, how do I know if I should |
| 5 |
>> mark it resolved or not before it is stable? |
| 6 |
> |
| 7 |
> If package is in stable to begin with, I would certainly prefer it not |
| 8 |
> to be marked fixed before it is in stable in all cases to avoid that |
| 9 |
> ambiguity. keywords are useful for search and filtering |
| 10 |
> |
| 11 |
|
| 12 |
That would of course work. The question is whether we're willing to |
| 13 |
live with that. It would mean that most bugs would stay open a lot |
| 14 |
longer than they do today. |
| 15 |
|
| 16 |
Also, in the case of STABLEREQs would we treat them more like security |
| 17 |
bugs - the last arch would just post a comment that all archs are |
| 18 |
stable and un-CC themselves, but leave the bug open to remind the |
| 19 |
maintainer to go check all open bugs to see if any should be marked |
| 20 |
fixed? |
| 21 |
|
| 22 |
|
| 23 |
-- |
| 24 |
Rich |
Archives