libc borked (and I stop testing)

[Milan Bouchet-Valat]

Vincenzo Ciancia a écrit :
> A possible idea to improve the situation is to have a "regression" tag,
> and to mark "high priority" all regressions. Say what you want, but this
> is *exactly* the behaviour that one would expect from any software
> distributor: things works, you break it, I tell you as soon as I
> discover it, you fix it as soon as possible because the bug is in the
> change you just made, so your change has to be fixed. If you let the
> regression there for three years, you'll have hysterical raisins when
> you put your hands back on that code. 
>   
+1

Would somebody that can set up new rules for Bug Squad, QA, Bug Control
and so on teams add the tag "regression" in the list of tags to use, and
shift policy so that every regression is marked as High priority? This
would at least help to sum up what should really be fixed, because often
these bugs are forgotten.

Cheers