Re: [cloud] #169: Spec for IRC bot to notify about blockers

2016-09-14 Thread Fedora Cloud Trac Tickets
#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 =>


-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org


Re: [cloud] #169: Spec for IRC bot to notify about blockers

2016-09-07 Thread Fedora Cloud Trac Tickets
#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 jberkus):

 This is being deferred pending completion of
 
https://fedoraproject.org/wiki/Changes/ReleaseEngineeringAutomationWorkflowEngine

 It will be revisited once that's up and running.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org


Re: [cloud] #169: Spec for IRC bot to notify about blockers

2016-09-03 Thread Personal (open)
 

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: 
> cloud 
> Fedora Cloud Working Group Ticketing System
> ___
> cloud mailing list
> cloud@lists.fedoraproject.org
> https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org [4]

-- 

Corey W Sheldon
ph: +1 (310).909.7672
0x8B4E89435A88E539 0x59276298D2264944

Freelance IT Consultant, Multi-Discipline Tutor
Fedora AmbaNA (linuxmodder)
Ameridea LLC Founder, President

Find me elsewhere:
https://gist.github.com/linux-modder/ac5dc6fa211315c633c9

"One must never underestimate the power of boredom...from which
creativity and laziness are borne, which can spark great works of chaos
and genius." --Anonymous

"Any man willing to retreat freedom for security is deserving of
neither." (Pp) -- Benjamin Franklin. 

This document, including attachments, is intended for the person or
company named and contains confidential and/or legally privileged
information. Unauthorized disclosure, copying or use of this information
may be unlawful and is prohibited. If you are not the intended
recipient, please destroy this message and notify the sender.
 

Links:
--
[1] https://fedorahosted.org/cloud/ticket/167
[2] https://fedorahosted.org/cloud/ticket/169
[3] https://fedorahosted.org/cloud
[4]
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org


Re: [cloud] #169: Spec for IRC bot to notify about blockers

2016-08-31 Thread Fedora Cloud Trac Tickets
#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 mattdm):

 That said, "image does not exist at all because it did not build", or
 "image does not boot" are almost certainly going to be blockers (for any
 image which is itself blocking).

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org


Re: [cloud] #169: Spec for IRC bot to notify about blockers

2016-08-31 Thread Fedora Cloud Trac Tickets
#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: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org