trafodion-technical-committee team mailing list archive

["Birdsall, Dave" <dave.birdsall@xxxxxx>]

Hi,

Renu and Atanu were asking for advice on how to mark Launchpad bugs that we think are fixed but aren't completely sure.

We'd like to ask the Technical Committee for advice.

Today, Launchpad has a status field with these values (I've taken this from https://wiki.trafodion.org/wiki/index.php/Bugs):

New     The bug was just created
Incomplete      The bug is waiting on input from the reporter
Confirmed       The bug was reproduced or confirmed as a genuine bug
Triaged         The bug comments contain a full analysis on how to properly fix the issue
In Progress     Work on the fix is in progress, bug has an assignee
Fix Committed   The branch containing the fix was merged into master
Fix Released    The fix is included in the milestone-proposed branch, a past milestone or a past release
Invalid         This is not a bug
Opinion         This is a valid issue, but it is the way it should be
Won't Fix       This is a valid issue, but we don't intend to fix that

So, if we've fixed a bug, the status field should be "Fix Committed". But what if we think it's fixed but we're not sure?

One possibility is to simply leave it as "Fix Committed", and count on someone to re-open it should the bug resurface. This would be a reasonable thing to do if we had an easy way to figure out what Launchpad cases have been fixed recently (say, since the last release point).

Another possibility is to create a new status, say, "Probable Fix Committed". I don't know how easy it is to add a new status to Launchpad (or if it is even possible).

Another possibility is to use a tag (see https://wiki.trafodion.org/wiki/index.php/Bug_Tags). These are easy to define. Today we are using tags to indicate what part of the software is affected, or how the bug manifests itself. We could add a new use, and add a tag, say, "probably-fixed".

What are your thoughts?

Thanks,

Dave