Comment 4 for bug 90738

On Thu, Mar 22, 2007 at 07:58:41AM -0000, Matthew Paul Thomas wrote:
> I suppose that a mass-change from Fix Committed to Fix Released, at
> release time, would be infeasible even if mass changes were implemented
> in Launchpad. For example, when NoMoreSourcePackages lets bugs be fixed
> on a mainline during a release's code freeze, not all bugs that happen
> to be Fix Committed on release day will have their fixes included in the
> release, and determining the subset that have been included would be too
> much work (as prefigured by the current dearth of distrorelease bug
> targeting you mentioned).
>
> I'm unclear about whether you think there is a *useful* distinction
> between "Fix Committed" and "Fix Released" at all. If so, how would the
> distinction help in daily work?

Fix Committed - To the maintainer, this usually means that the bug doesn't
need any further attention. The fix will be included in the next release
they do, without any further action on their part. They might review the
list of Fix Committed bugs to decide whether there is enough there to
justify rolling a new release, or if they will wait until later. To another
developer, it means that they don't need to concern themselves with this bug
at all, because a fix has already been accepted into the tree. To the user,
it means that the bug is known, and a fix is on the way with the next
version of the package. People still see the bug, but have no reason to
act on it.

Fix Released - The fix has been incorporated into a release, and is believed
to be fully resolved. If anyone sees the bug in the current version, they
should take action and seek to reopen the bug report.

--
 - mdz