Blockers via flags?
awilliam at redhat.com
Sun May 16 10:26:00 UTC 2010
On Tue, 2010-05-11 at 10:31 -0700, Jesse Keating wrote:
> > What you'd loose with using flags is the "distro version" context.
> Erm, the bug would be filed against a particular version. EG the bug
> has to be filed against Fedora 14 in order to be able to use flags to
> mark it as a blocker for Fedora 14. Bugs filed against rawhide wouldn't
> necessarily be able to set flags (although that's an interesting
> discussion to have)
This could give us a problem; remember, bugs in preupgrade and
livecd-tools in F(N-1) can block F(N) (as is the case with F13, and was
the case with F12).
I also agree that the issue of flags doesn't really come into the issue
of how we process blockers; the fact that currently we do it almost
entirely synchronously in a meeting isn't really anything to do with
whether we use flags or not, it's just...how we do it. We could easily
do it async at the moment with comments, but we just don't.
Overall, though, I'm fine with this idea. As I said last time we
discussed it, my principal objection is that it hurts our efforts to get
people to buy into the process in the short term, but I can live with
the idea that in the long-term the benefits will be enough to counteract
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
More information about the devel