Triaging and planning changes

Curtis Hovey-Canonical curtis at canonical.com
Thu May 8 18:38:22 UTC 2014


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



More information about the Juju-dev mailing list