Re: [Kicad-developers] GitLab bug workflow

On 12/4/19 12:16 PM, Ian McInerney wrote: [...] > Speaking of which @Maciej Suminski  can > you modify the current janitor "nudger" that emails people if they close > an issue with no milestone to work with GitLab? Consider it done. KiCad Bot is now configured to

Re: [Kicad-developers] GitLab bug workflow

Hi, On Wed, Dec 04, 2019 at 11:09:58AM +, Jeff Young 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? Can't gitlab track bugs vs commits, and generate open/closed states for the

Re: [Kicad-developers] GitLab bug workflow

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 wrote: > > The plan that has been proposed here: >

Re: [Kicad-developers] GitLab bug workflow

The plan that has been proposed here: 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

Re: [Kicad-developers] GitLab bug workflow

Hmm… just noticed that some of the non-released bugs are coming in a Closed, so we appear to be going from Open to Closed at Fix-Committed. So do we still want to add the Fix-Committed tag to new bugs, or just Close them? > On 4 Dec 2019, at 11:09, Jeff Young wrote: > > Forgive me if this

[Kicad-developers] GitLab bug workflow

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.