kicad-developers team mailing list archive

[Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>]

This sounds like a step up from what we're doing now.

On Thu, Mar 12, 2015 at 10:38 AM, Wayne Stambaugh <stambaughw@xxxxxxxxx>
wrote:

> There was a question asking how bugs are closed.
>
> https://answers.launchpad.net/kicad/+question/263366
>
> I didn't have a good answer so I dug around a bit and found some
> information on the Launchpad blog about the meaning of bug status tags.
>
> http://blog.launchpad.net/general/of-bugs-and-statuses
>
> I also changed the status of two bugs from "Fix Committed" to "Fix
> Released" and the "Open Bug" count was reduced by two.  Given the way we
> have been handling bugs, it looks like none of bugs are ever fixed.
> This is confusing for new developers and doesn't really make a lot of
> sense.  I am proposing that we change the way we handle bugs as follows:
>
> * Once a bug fix has been committed to the project branch it should be
> tagged as "Fix Committed" as we have always done.
>
> * The bug report status should be changed to "Fix Released" once bug is
> confirmed as fixed by someone other than the person that authored the
> bug fix.  I'm assuming bugs can be changed back to "New" if the
> committed fix did not actually fix the bug but I haven't tried it yet.
>
> * For legacy bug fixes, if the "Fix Committed" date is over a month, it
> can be changed to "Fix Released" even if the fix has not been confirmed
> as long as there are no additional complaints after the committed fix.
>
> If anyone has any comments, please speak up.  Once we have a consensus
> on this, I will make it an official project policy.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>