Re: [ACTION REQUIRED v3] Retiring packages for F-17

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 2012-01-29 at 22:21 +0100, Michael Schwendt wrote:

> > What's needed to be sure the bug doesn't get closed is for the Version
> > field to be bumped to a release that's not going EOL. A comment may do
> > the job, but there's usually hundreds of bugs in the list to be EOLed
> > and it's usually a single person compiling the EOL list; they don't have
> > time to inspect _every_ ticket manually (the weeding is more along the
> > lines of 'look through the summary list for bugs that look like they may
> > be special cases').
> 
> qed ;-)

What was demonstrandumed exactly? You say "The process is flawed,
however, if tickets that get updated appropriately, don't result in a
higher priority or are not taken off the bug zapper list"; the question
is what constitutes 'appropriately'. It's very difficult to construct a
search such that a *comment* that a bug is still valid is considered to
render it un-EOL-able, while not causing a bunch of false positives.

> Would a special tag in the bug summary be helpful?

> Or a keyword that would exclude the ticket from the compiled list
> automatically? If a second search on all tickets with that keyword
> results in hundreds or thousands of ticket numbers, that should raise
> an alarm-bell.

We do use this kind of system for the Rawhide rebase - bugs with the
FutureFeature keyword (or RFE in the summary) are excluded. I'm not
actually sure if there's a similar keyword for the EOL search, because
the actual EOL search doesn't appear to be documented anywhere,
unfortunately - there's no SOP for it and it's not in
https://bugzilla.redhat.com/userprefs.cgi?tab=saved-searches that I can
see. Note that it's the program manager who's actually in charge of
doing the EOL stuff - so it was poelcat for a long time, and now it's
The Berge. Robyn, maybe we could improve this? We did have a thread a
while back about improving documentation of the housekeeping tasks, but
never got around to it.

> It's sad to talk to Fedora users (and ex-Fedora users), who have made
> bad experience in bugzilla related to this.

-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux