| 1 |
On 08/15/2016 03:21 AM, Kristian Fiskerstrand wrote: |
| 2 |
> Better than developers marking it fixed without it hitting stable as too |
| 3 |
> many are doing today. |
| 4 |
Totally guilty of that one, sorry! |
| 5 |
|
| 6 |
I think adding a status would be great. We could have CONFIRMED and even |
| 7 |
RESOLVED still, but the goalpost could be moved to CONFIRMED/STABLE |
| 8 |
instead of CONFIRMED/RESOLVED. Pushing the fix to git can still resolve |
| 9 |
a problem, but the STABLE status would mean that the package that fixed |
| 10 |
the bug then hit stable. |
| 11 |
|
| 12 |
The problem with this, however, is that it turns every bug into the |
| 13 |
subject of the bug *and* a stabilization bug. Are we to get rid of |
| 14 |
stabilization bugs altogether? Or do we keep stabilization bugs and |
| 15 |
merely update all the dependent bugs to CONFIRMED/STABLE once |
| 16 |
stabilization happens? |
| 17 |
|
| 18 |
A workflow suggestion would be great, because I care about fixing my |
| 19 |
bugs and getting them to users as fast as what's reasonable. |
| 20 |
|
| 21 |
(That said I have a busy weekend ahead of me with lighttpd...) |
| 22 |
|
| 23 |
-- |
| 24 |
Daniel Campbell - Gentoo Developer |
| 25 |
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
| 26 |
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |
Archives