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