Status "FixCommited" for ubuntu-tasks

[Murat Gunes]

On Wed, 15 Apr 2009 00:33 +0100, "Max Bowsher" <maxb at f2s.com> wrote:

> I don't think a fix upstream should qualify an ubuntu-task for "Fix
> Committed", because it's an indication of the amount of work remaining
> - "Fix Committed" implies that the fix will arrive with no further
>   development work, just releasing/uploading. Whereas, integrating a
>   new upstream version may require lots of packaging work, or be
>   impossible during a freeze.

Agreed; it's best to keep the status as "Triaged". That means the the
report has been evaluated and there's nothing more to be done by the
reporter or triager, but there's still work to be done by a developer.

Another point is that the presence of a fix somewhere in the upstream
VCS does not necessarily mean that it will be included in the upstream
release, which will in turn end up in Ubuntu. Further changes may occur
that can revert or modify the fix, or there may be independent patches
(such as in Debian) that interfere with it or revert it. The logic of
using "Fix Committed" in accordance with its literal meaning can also be
extended to mean that a fix has been committed anywhere in the VCS (such
as an independent branch), which again will complicate things.

> > If the latter is the majority opinion here, we should discuss having
> > a new status in malone, e.g. called "FixedUpstream" to easily spot
> > already fixed bugs.
>
> Surely the canonical way to describe that in Malone is with an
> upstream bugtask?
>
> Duplicating the ways in which you can represent that information seems
> like it could get messy.

The combination of "Fix Released" upstream and "Triaged" in Ubuntu
should be enough to indicate that the fix is set to land in Ubuntu.

m.