Triaging and planning changes

[Curtis Hovey-Canonical]

juju-qa-bot has will be doing mass/automated bug changes for us now.
You can filter those bug emails out since they will be usually be a
case of bugs changing to Fix Committed or Fix Released. I am also
tasking to bot to create the pool of Medium bugs tat we will actively
retriage.

On Fri, May 9, 2014 at 12:28 AM, John Meinel <john at arbash-meinel.com> wrote:
> So I think a couple of the key flows are
> 1) next-stable is intended to be a list of bugs that get burned down, so to
> move a bug into next-stable, you should really take a different bug out
> 2) the 75 high bugs are intended as a pool that we will try to stay aware
> of. So as we move bugs out of here (as they are fixed, etc) other bugs get
> promoted to high.

> I'm not 100% sure about the horizon milestone.

Let's try without a horizon milestone. my concern was a clear
distinction between targeted and untargeted bugs. Lp doesn't make this
distinction; a listing of High bugs will include bugs with and without
milestones. It is impossible to query for no milestone. The listing
will always include Fix Committed. So we will see the next-stable
burndown list intermingled in the high. This is the smallest URL I
could construct to show a listing of High bugs, the untargeted bugs
are listed first. There are 165 bugs at this moment, 87 of which are
are High without a milestone.
    https://bugs.launchpad.net/juju-core/+bugs?field.importance=High&field.status=Triaged&field.status=In%20Progress&orderby=-milestone_name

> That would give us
> 1) A new bug comes in, I review it and mark it as High
> 2) That flags it for review. It should be either moved into Horizon or
> demoted to Medium

Just demoted to Medium.

> or
> 1) A new bug comes in, it gets reviewed as Low and stays in the backlog pool
>
> or
> 1) A new bug comes in, it gets reviewed as Medium
> 2) A couple of High bugs get completed so we look over the Medium bugs

We have more that 75 High. bugs. We can demote 12 bugs or wait a week
for them to burn down (ban new high bugs)

We current'y have all the High bugs targeted to the next-stable
milestone. Team Leads need to review the list and untarget the
unrequired bugs. This will also require us to demote some bugs to
Medium.

I have some concern about current developer behaviour with bugs that
will lead to a lot of churn of High bugs without milestones. New
habits are needed. Developers often report a bug and start working on
it, regardless of its importance. I am sure the developer is operating
under the opportunity situation where this is the moment to fix a bug.
Since there will always be 75 high bugs, when developers report the
bug as high, then need to demote a bug to Medium. That is both a
distraction for developers and bug subscribers. Developers could
report the bug as Medium, work on it because it is an opportunity. We
can demote the unfinished bug to low during retriage if we don't see
any progress with the bug.


-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui