Triaging and planning changes

[John Meinel]

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. Though I would be happy to
triage bugs as they come in to my personal understanding of importance, and
then have someone else responsible for the actual "yes this is more
important than our current ones, so bump this bug out, and pull this bug
in".

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

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 and
pull some into High+Horizon

Sounds great to me, but with the above I don't have to maintain the
milestones so I worry about just passing the buck.

John
=:->


On Thu, May 8, 2014 at 10:38 PM, Curtis Hovey-Canonical <
curtis at canonical.com> wrote:

> We agreed to change how we triage bugs and manage milestones to make
> it easier to focus on our current and next priorities.
>
> We will maintain a list of 75 high bug, a single page listing on Lp.
> We will manage 4 milestones:
>     Current stable point (1.18.3):
>         https://launchpad.net/juju-core/+milestone/1.18.3
>         all fixed bugs and those that must be fixed for the release
>     Current devel point (1.19.2)
>         https://launchpad.net/juju-core/+milestone/1.19.2
>         all fixed bugs and those that must be fixed for the release
>     Next Stable:
>         https://launchpad.net/juju-core/+milestone/next-stable
>         all high bugs that define the stable release
>     Horizon:
>         https://launchpad.net/juju-core/+milestone/horizon
>         all remaining high bugs
>
> We expect this practice will help us deliver predictable and timely fixes.
>
> We will regularly review the medium bugs. Some will be promoted to
> High. The older bugs will be demoted to Low. We haven't set a time We
> haven't set an age to demote the bugs. There are just 6 High bugs (we
> haven't demoted yet) that older than a year.
>
> Importances
>     Critical: do now; place in the front of the queue
>     High: do soon; place in the queue
>     Medium: do when there is an opportunity and retriage when planning
>     Low: do when there is an opportunity.
>
> We need to re-triage our bugs now. Ian has a short list of bugs that
> will go to Next or Horizon. There are 49 bugs targeted to
>     https://launchpad.net/juju-core/+milestone/1.20.0
> ...probably too many to keep high. I propose all the bugs targeted to
>     https://launchpad.net/juju-core/+milestone/2.0
> be demoted to medium. All high bugs not assigned to a milestone will
> be demoted to medium.
>
>
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140509/3110b8d4/attachment.html>