#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.

On 31.08.2016 18:46, Fedora Cloud Trac Tickets wrote:

#169: Spec for IRC bot to notify about blockers ---------------------+--------------------- Reporter: jberkus | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting ---------------------+--------------------- One of the issues we have with release blockers is slow response by the fedora-cloud WG. As that group is very IRC-centric, we'd like to have some form of notification via IRC when a release blocker is encountered.

Here's a draft spec, please revise:

1. whenever a release blocker issue is filed or updated, a message will be

sent via bot to the #fedora-cloud channel;

Could adding it to a 'active archives' style group like posterious has work for this? Or even just a fedmsg hook?

2. the /topic of #fedora-cloud will be updated with a list of release-

blocker issues once a day.

Why not just have a short link or static link in the /topic that redirects / takes you to the bug tracker page, with the newest/most critical etc set already as search params?

Questions: how do we identify release-blocker issues?

This relates to issue https://fedorahosted.org/cloud/ticket/167 [1]

-- Ticket URL: <https://fedorahosted.org/cloud/ticket/169 [2]> cloud <https://fedorahosted.org/cloud [3]> Fedora Cloud Working Group Ticketing System _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org [4]

#169: Spec for IRC bot to notify about blockers ---------------------+--------------------- Reporter: jberkus | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: | ---------------------+--------------------- Changes (by sayanchowdhury):

* keywords: meeting =>