[rfc] Fix committed/released distinction

[Martin Pool]

At present we just mark bugs fix released when they are merged to trunk. The
kanban view<http://people.canonical.com/~mbp/kanban/canonical-bazaar-kanban.html>is
making me wonder if we should in fact distinguish them, so we see how
much work is not yet finally finished. It might be especially good for
stable series tasks, where there can be more latency and more discretion
between committing and releasing.

This would make bzr consistent with what is done by some other related
projects including some (many?) kanbans.

Doing this creates a bit of work:

- we need to run a script to flip things to released when that becomes true
(not built in to lp but obviously automatable)

- update some docs

- retrain muscles

I think we should not worry about refiling existing bugs, but rather just do
this from this point on.

Any comments/objections?

Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/bazaar/attachments/20110408/1c208d89/attachment.html>