Re: [Kicad-developers] GitLab migration

2019-12-04 Thread Marco Ciampa
On Wed, Dec 04, 2019 at 08:20:21AM -0500, Wayne Stambaugh wrote: > Eventually, all official KiCad repositories will be migrated to GitLab. > I think the documentation and translation repos have already been > migrated from GitHub. Yes and you (all devs) did a GREAT work! Many thanks! --

[Kicad-developers] Pending patches and merge requests

2019-12-04 Thread Wayne Stambaugh
Now that GitLab is live, if you have any pending patches on the mailing list and/or any pending Launchpad merge requests would you please submit a merge request on GitLab. We are going to try to use the GitLab merge request feature because it provides some useful features such as build and code

[Kicad-developers] GitLab is live

2019-12-04 Thread Wayne Stambaugh
The GitLab transition is complete and the Launchpad bug tracker has been disabled. Please use the GitLab KiCad issue tracker[1] to report bugs. Thank you for your patience during the transition. Cheers, Wayne [1]: https://gitlab.com/kicad/code/kicad/issues

Re: [Kicad-developers] Strokefont change from std::deque to std::vector

2019-12-04 Thread Seth Hillbrand
On 12/3/19 9:46 AM, Jeff Young wrote: OK, my stuff is pushed On 3 Dec 2019, at 17:44, Jeff Young > wrote: He he… I had sort of the same idea, only I’m building it lazily at runtime.  But I think your idea would be even better. Since I’ve already made the changes

Re: [Kicad-developers] Launchpad bug tracker

2019-12-04 Thread Maciej Suminski
Hi Adam, No worries, the report is fine [1]. Cheers, Orson 1. https://gitlab.com/kicad/code/kicad/issues/3636 On 12/4/19 5:28 PM, Adam Wolf wrote: > Sorry folks, I forgot about the Gitlab migration and responded to a > bug on Launchpad. I hope I have not generated too much extra work. > >

[Kicad-developers] Launchpad bug tracker

2019-12-04 Thread Adam Wolf
Sorry folks, I forgot about the Gitlab migration and responded to a bug on Launchpad. I hope I have not generated too much extra work. https://bugs.launchpad.net/kicad/+bug/1855118 Adam ___ Mailing list: https://launchpad.net/~kicad-developers Post

Re: [Kicad-developers] GitLab migration

2019-12-04 Thread Wayne Stambaugh
Hi Seppe, On 12/3/19 6:39 PM, Seppe Stas wrote: > Just wanted to say I love this and I'm sure it will improve visibility > of the KiCad project and lower the barrier of entry for new developers. We shall see. I'm probably a less optimistic about this. The main reason for the move was to make

Re: [Kicad-developers] Project leader announcement

2019-12-04 Thread Marco Ciampa
That's great! Congrats Wayne! -- Saluton, Marco Ciampa ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help :

Re: [Kicad-developers] GitLab bug workflow

2019-12-04 Thread Simon Richter
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

2019-12-04 Thread Jeff Young
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] Project leader announcement

2019-12-04 Thread Tomasz Wlostowski
On 03/12/2019 15:28, Wayne Stambaugh wrote: > I am excited to announce that I have joined the > KiCad Services Corporation[1] Congratulations Wayne! Tom ___ Mailing list: https://launchpad.net/~kicad-developers Post to :

Re: [Kicad-developers] GitLab bug workflow

2019-12-04 Thread Ian McInerney
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

2019-12-04 Thread Jeff Young
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

2019-12-04 Thread Jeff Young
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.