Kanban view still relevant? Bug statuses?

[Kapil Thangavelu]

The milestone centric kanban view moved things that where approved or fix
committed into a needs release column.

http://people.canonical.com/~niemeyer/florence.html

We're no longer using the kanban view for py juju, and go juju seems to be
gravitating towards blueprints from what i've heard.

The move to release urls, non distro distribution makes the distinction of
committed / released a little different (ie more fluid) though still apt.

-k



On Fri, Jun 22, 2012 at 2:48 PM, Clint Byrum <clint at ubuntu.com> wrote:

> As we have a release process now, I'd like users to be able to track
> bugs Released versus bugs Committed. This helps us know what is going
> into the next release. The milestone bugs is also helpful, but there
> are often other fixes that were not milestoned that go in.
>
> However, IIRC, the Kanban view used Fix Committed to mean that a bug
> wasn't being actively worked on anymore, and was more in a review
> state. Is that still true? Is the Kanban even relevant anymore?
>
> Thanks!
>
> --
> 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/20120622/5cf39ef8/attachment.html>