kicad-developers team mailing list archive

[Jeff Young <jeff@xxxxxxxxx>]

It would definitely streamline the workflow if we could be good about assigning milestones (and deep-six the fix-committed/fix-released tags).

> On 4 Dec 2019, at 11:16, Ian McInerney <Ian.S.McInerney@xxxxxxxx> wrote:
> 
> The plan that has been proposed here: https://gitlab.com/kicad/code/kicad/wikis/Developers/Guidelines/Issue-Tracker <https://gitlab.com/kicad/code/kicad/wikis/Developers/Guidelines/Issue-Tracker> is that bugs in fix-committed, fix-released, fixed and duplicate will be in the closed status. I had added the fix-committed/fix-released to our GitLab tags so we can still keep track of if something has actually been released. If we promise to be good about assigning bugs to milestones, then we could just use milestones being released to mark them as released/committed (an open milestone is not released, a closed one is).
> 
> Speaking of which @Maciej Suminski <mailto:maciej.suminski@xxxxxxx> can you modify the current janitor "nudger" that emails people if they close an issue with no milestone to work with GitLab?
> 
> -Ian
> 
> On Wed, Dec 4, 2019 at 11:10 AM Jeff Young <jeff@xxxxxxxxx <mailto:jeff@xxxxxxxxx>> wrote:
> Forgive me if this was communicated and I missed it, but when do we transition a GitLab bug from Open to Closed?  At Fix-Committed or Fix-Released?
> 
> And are those two tags just for migrated bugs, or will we continue to use them for new bugs?
> 
> Thanks,
> Jeff.
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> More help   : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>