On Fri, 2011-07-29 at 08:29 -0400, James Laska wrote: > > 3. If 'no' to question 2, do people think we need to do some sort of > > review and notification outside of the blocker meetings and updating the > > bugs themselves? If so, what? > > Daily/frequent review of the bugs outside the meeting is an important > activity that I haven't documented very well. It's something I've been > doing regularly (behind-the-scenes) leading up to each of the important > milestones. Given the rapid and short release cycle ... I'm convinced > this is a key contributor to releasing on time. I don't have a hard > script that I follow, but it typically involves me reaching out to > maintainers for feedback/ETA/updates on IRC, bugzilla or email. > Sometimes someone else in #fedora-qa will offer to check-in on a bug. > Either way, this has proven very helpful to re-prioritize resources in > the event a developer is busy, sick or on vacation. This also helps > flush out any differences in perceived priority between maintainer and > release criteria. Yeah, I do the same thing. I think the description in the schedule is a bit vague, and can easily be taken to refer more to a process of 'take a list of blocker bugs and post it to an email list' rather than the more case-by-case, directly-via-bugzilla approach we've been using lately. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
