We have discussed this before. The current policy is to mark bugs as fix committed when the bug fix has been committed to either the product or the current stable release repo. Once the next stable release is rolled out, the fix committed bug reports should be changed to fixed released. If for some reason we need to change this policy, we should define and document the changes.
On 5/31/2016 12:35 PM, Nick Østergaard wrote: > I that that it is ok to mark as released when it was introduced and > fixed in one dev cycle. That is that it never was a bug in a release. > > 2016-05-31 18:12 GMT+02:00 Simon Wells <swel...@gmail.com>: >> I know that bugs should be fix commited until a new version is >> released that has the bug fix in it. But IF a bug was only introduced >> in the product repo and subsequently fixed >> >> https://bugs.launchpad.net/kicad/+bug/1523933 >> >> as seen in this bug which was Introduced in 6352 fixed in 6359 the >> version that caused the issue is just as "released" as the version >> that fixed the issue does it not make sense to mark this as fix >> released and other similar bugs >> >> thanks >> >> Simon >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
