----- "Matthias Clasen" <mclasen(a)redhat.com> wrote:
On Fri, 2010-02-26 at 13:16 +0100, Kevin Kofler wrote:
I think banning stable pushes is the right idea. None of your reasons
is
very convincing.
My packages are rarely tested and I forget them in testing phase for a
long time. Also fixing BR don't need testing. I simply need push
immediately the new/fixed package.
The process of updates is right now inconvenient and it could lead to
more bugs fixed as 'closed in rawhide'.
> * A regression which causes big breakage at least for some
people
slipped
> through testing for whatever reason. We urgently want the fix to get
out
> ASAP.
But presumably we still want to test the fix, to avoid introducing
yet
another regression ?!
> * A regression slipped through testing for whatever reason and the
patch is
> trivial. We want the fix to get out ASAP, and the risk of breakage
is very
> low.
Just go up to your first argument: the breage slips through. That is
exactly what happens if your judgement of 'low risk' turns out to be
wrong. And it will...
> * A trivial bugfix (like a one-line diff), tested and confirmed to
fix the
> bug by at least one person. The risk of breakage is extremely low.
Again: go up. Breakage always happens to somebody else. That one
person
tested the fix is not enough.
Matthias
--
devel mailing list
devel(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel