subject:"Unstuck QA bot"

Re: Unstuck QA bot

2012-12-13 Thread Enis Söztutar

Thanks Todd. On Thu, Dec 13, 2012 at 9:44 AM, Nick Dimiduk wrote: > Thanks Todd! > > On Wed, Dec 12, 2012 at 6:34 PM, Todd Lipcon wrote: > > > The QA bot was previously pointing at a JIRA filter which matched all > > Patch Available issues. That number has grown to >300 across the many > > pro

Re: Unstuck QA bot

2012-12-12 Thread Karthik Kambatla

Brilliant! Thanks Todd. On Wed, Dec 12, 2012 at 8:39 PM, Stack wrote: > Thanks Todd. > St.Ack > > > On Wed, Dec 12, 2012 at 6:34 PM, Todd Lipcon wrote: > > > The QA bot was previously pointing at a JIRA filter which matched all > > Patch Available issues. That number has grown to >300 across th

Re: Unstuck QA bot

2012-12-12 Thread Stack

Thanks Todd. St.Ack On Wed, Dec 12, 2012 at 6:34 PM, Todd Lipcon wrote: > The QA bot was previously pointing at a JIRA filter which matched all > Patch Available issues. That number has grown to >300 across the many > projects that the QA bot works on. Unfortunately, that meant that a > lot of

Unstuck QA bot

2012-12-12 Thread Todd Lipcon

The QA bot was previously pointing at a JIRA filter which matched all Patch Available issues. That number has grown to >300 across the many projects that the QA bot works on. Unfortunately, that meant that a lot of the newer JIRAs (especially in alphabetically lower projects like HBASE, HADOOP, and