#169: Spec for IRC bot to notify about blockers
---------------------+---------------------
Reporter: jberkus | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Resolution:
Keywords: meeting |
---------------------+---------------------
Comment (by adamwill):
Well, there's no straightforward way to identify 'cloud release blockers';
we do not segment them by product in any way.
Blocker bugs are handled with tracker bugs in Bugzilla. Three trackers are
filed for each release: one for Alpha, one for Beta, one for Final. They
are given standard aliases: F(rel)AlphaBlocker , F(rel)BetaBlocker,
F(rel)FinalBlocker , where (rel) is the release number. So currently we
have F25AlphaBlocker, F25BetaBlocker, and F25FinalBlocker.
Any bug blocking one of those trackers is either a proposed or an accepted
blocker. If it has 'AcceptedBlocker', 'Accepted0Day' or
'AcceptedPreviousRelease' in its whiteboard field, it's an accepted
blocker. If it does not, it's a proposed blocker.
There's a webapp called 'blockerbugs' -
https://qa.fedoraproject.org/blockerbugs - which we (QA) use for
convenience in dealing with blockers. It handles a lot of the work of
identifying blockers for upcoming cycles. Off the top of my head I don't
know if it has an API, and I also don't know if anything sends out
fedmsg's for proposed / accepted blockers.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/169#comment:1>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
