[Kicad-developers] How sophisticated is the bug closure script?
On 07/15/2018 11:20 PM, Jeff Young wrote: > Hi Orson, > > I was asking about the Fix Committed -> Fix Released script (assuming it is a > script), rather than the *** -> Fix Committed script. Frankly, I could not recall how we have updated the bug statuses after the previous release. This time we used a script, and it should not be very hard to modify it to filter bugs targeted at a particular release. It will require some discipline in setting appropriate targets in bug reports though. > Although your answer does bring up the question, do we want to setup the > Janitor script to handle the 5.1 branch as well, or just do them by hand? I guess 5.1 will become the master branch soon, so KiCad Janitor will cope with updating bug statuses when it happens. As far as I understand we will only have 5.0 and master (aka 5.1) branches in the near future. Cheers, Orson > Cheers, > Jeff. > >> On 15 Jul 2018, at 22:11, Maciej Suminski wrote: >> >> Hi Jeff, >> >> KiCad Janitor follows only the master branch and does not take tags or >> target milestones into account. The rules are very simple: whenever >> there is a "fixes" line, change the correlated bug status to "Fixed". >> Have a look at the script [1], I will be happy to improve it. >> >> Cheers, >> Orson >> >> 1. https://git.launchpad.net/kicad-git-hook/tree/hook.py >> >> On 07/15/2018 05:43 PM, Jeff Young wrote: >>> In particular, can I go ahead and make commits that have “fixes” lines (as >>> long as the bugs are tagged 5.1), or do I need to wait till be auto-close >>> the 5.0 bugs? >>> ___ >>> 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 > signature.asc Description: OpenPGP digital signature ___ 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
Re: [Kicad-developers] How sophisticated is the bug closure script?
Hi Orson, I was asking about the Fix Committed -> Fix Released script (assuming it is a script), rather than the *** -> Fix Committed script. Although your answer does bring up the question, do we want to setup the Janitor script to handle the 5.1 branch as well, or just do them by hand? Cheers, Jeff. > On 15 Jul 2018, at 22:11, Maciej Suminski wrote: > > Hi Jeff, > > KiCad Janitor follows only the master branch and does not take tags or > target milestones into account. The rules are very simple: whenever > there is a "fixes" line, change the correlated bug status to "Fixed". > Have a look at the script [1], I will be happy to improve it. > > Cheers, > Orson > > 1. https://git.launchpad.net/kicad-git-hook/tree/hook.py > > On 07/15/2018 05:43 PM, Jeff Young wrote: >> In particular, can I go ahead and make commits that have “fixes” lines (as >> long as the bugs are tagged 5.1), or do I need to wait till be auto-close >> the 5.0 bugs? >> ___ >> 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
Re: [Kicad-developers] How sophisticated is the bug closure script?
Hi Jeff, KiCad Janitor follows only the master branch and does not take tags or target milestones into account. The rules are very simple: whenever there is a "fixes" line, change the correlated bug status to "Fixed". Have a look at the script [1], I will be happy to improve it. Cheers, Orson 1. https://git.launchpad.net/kicad-git-hook/tree/hook.py On 07/15/2018 05:43 PM, Jeff Young wrote: > In particular, can I go ahead and make commits that have “fixes” lines (as > long as the bugs are tagged 5.1), or do I need to wait till be auto-close the > 5.0 bugs? > ___ > 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
[Kicad-developers] How sophisticated is the bug closure script?
In particular, can I go ahead and make commits that have “fixes” lines (as long as the bugs are tagged 5.1), or do I need to wait till be auto-close the 5.0 bugs? ___ 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
