when are bugs closed?

This is a good question that I wish I had a better answer to give you. Currently, we used the "Fix Committed" status to indicated that a bug fix has been committed to the development branch. Technically the status of these bugs should change to "Fix Released" after the next stable release of KiCad. Although this is mostly semantics since most users are already using the development branch. I've read the launchpad bug documentation and I don't really see anything that represents the traditional bug tracker notion of a closed bug. For the project bugs with the "Fix Committed" status are closed for the development branch and bugs with the "Fix Released" are closed for all branches up to and including the associated branch. Bugs with the "Invalid" and "Wont Fix" status can also be considered closed.

Thanks for the info. The statistics on the right side of the main
LaunchPad bugs page show:

399 New bugs
1153 Open bugs
14 In-progress bugs
16 Critical bugs
34 High importance bugs
11 Incomplete bugs (can expire)

And the first thing you see when you load the bugs page is a whole bunch
of bugs marked "Critical" and "Fix Committed". It seems like if there
was a way to mark them closed then maybe they wouldn't show up on the
landing page, distracting from the actual active bugs.

No big deal, I was mostly looking for more info to get a sense for how
KiCad development works as I start to use it more.

-s

On Wed, Mar 11, 2015, at 11:01 PM, Wayne Stambaugh wrote:
> Your question #263366 on KiCad changed:
> https://answers.launchpad.net/kicad/+question/263366
>
> Status: Open => Answered
>
> Wayne Stambaugh proposed the following answer:
> This is a good question that I wish I had a better answer to give you.
> Currently, we used the "Fix Committed" status to indicated that a bug
> fix has been committed to the development branch. Technically the
> status of these bugs should change to "Fix Released" after the next
> stable release of KiCad. Although this is mostly semantics since most
> users are already using the development branch. I've read the launchpad
> bug documentation and I don't really see anything that represents the
> traditional bug tracker notion of a closed bug. For the project bugs
> with the "Fix Committed" status are closed for the development branch
> and bugs with the "Fix Released" are closed for all branches up to and
> including the associated branch. Bugs with the "Invalid" and "Wont Fix"
> status can also be considered closed.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/kicad/+question/263366/+confirm?answer_id=0
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/kicad/+question/263366
>
> You received this question notification because you asked the question.

I played around with changing a few bugs marked as "Fix Committed" to "Fix Released" and sure enough the "Open Bugs" count went down. I found some information on the Lauchpad blog about the meaning of the bug status tags and "Fix Released" is defined as:

Fix Released (This Revolution Is Over!)
This status is meant to communicate that the bug fix has been made available in a released form to the general public. The key meaning of this status is public availability; end-users can expect to download or access an updated version of the software that contains the change.

The key point to me is the bug fix is available to the general public. Any fix committed to the product branch of KiCad is available to the general public. Now that we have nightly builds, technically once the nightly build is complete and uploaded to a server, a bugs status should change from "Fix Committed" to "Fix Release". I will give some more thought to this and check with the other developers to see if we can come up with a better policy for closing bug reports.

One idea would be that the status becomes "Fix Committed" when a
developer commits the fix (seems reasonable), and then gets changed to
"Fix Released" when the fix is tested and confirmed by someone else on
the team. Not sure if that works in the KiCad dev flow, so take with a
grain of salt.

-s

On Fri, Mar 13, 2015, at 12:16 AM, Wayne Stambaugh wrote:
> Your question #263366 on KiCad changed:
> https://answers.launchpad.net/kicad/+question/263366
>
> Wayne Stambaugh posted a new comment:
> I played around with changing a few bugs marked as "Fix Committed" to
> "Fix Released" and sure enough the "Open Bugs" count went down. I found
> some information on the Lauchpad blog about the meaning of the bug
> status tags and "Fix Released" is defined as:
>
> Fix Released (This Revolution Is Over!)
> This status is meant to communicate that the bug fix has been made
> available in a released form to the general public. The key meaning of
> this status is public availability; end-users can expect to download or
> access an updated version of the software that contains the change.
>
> The key point to me is the bug fix is available to the general public.
> Any fix committed to the product branch of KiCad is available to the
> general public. Now that we have nightly builds, technically once the
> nightly build is complete and uploaded to a server, a bugs status should
> change from "Fix Committed" to "Fix Release". I will give some more
> thought to this and check with the other developers to see if we can
> come up with a better policy for closing bug reports.
>
> --
> You received this question notification because you asked the question.

This question was expired because it remained in the 'Open' state without activity for the last 15 days.