Just a quick heads up. The development branch of kicad is open so feel
free to push bug fixes as we work towards rc2.
Thanks,
Wayne
On 02/24/2018 07:53 PM, Wayne Stambaugh wrote:
It didn't take much to convince me. I've made the changes. We are
still at rc1 and marching on to rc2.
I’ll be eradicating the global g_UserUnit for 6.0, but it won’t be in 5.0.
Cheers,
Jeff.
> On 25 Feb 2018, at 08:35, Andrey Kuznetsov wrote:
>
> I thought there was also variable renaming, can't remember if it was global
> variables or other variables.
>
> On Sun, Feb
I thought there was also variable renaming, can't remember if it was global
variables or other variables.
On Sun, Feb 25, 2018 at 12:31 AM, jp charras wrote:
> Le 25/02/2018 à 03:12, Andrey Kuznetsov a écrit :
> > Just curious, a month back there were some emails
Le 25/02/2018 à 03:12, Andrey Kuznetsov a écrit :
> Just curious, a month back there were some emails discussing about major
> variable renames, it was
> decided to wait until people finished committing major features to avoid
> rebasing every patch.
>
> Has this been done?
>
Are you talking
Just curious, a month back there were some emails discussing about major
variable renames, it was decided to wait until people finished committing
major features to avoid rebasing every patch.
Has this been done?
On Sat, Feb 24, 2018 at 3:30 PM, Wayne Stambaugh
wrote:
> I
I think for v4 we forked when there was agreement that all was good;
new features
like the new 3D viewer and 3D plugins simply had to be developed separately
and merged after the v4 fork. For me this is the only process which makes sense;
forking so early on is a nuisance to everyone including any
It didn't take much to convince me. I've made the changes. We are
still at rc1 and marching on to rc2.
Cheers,
Wayne
On 02/24/2018 06:37 PM, Jon Evans wrote:
I would also recommend keeping 5.0 in master (and just use tags for the
RCs) to keep things simpler. I think we don't have enough
I would also recommend keeping 5.0 in master (and just use tags for the
RCs) to keep things simpler. I think we don't have enough committers and QA
process to handle two parallel branches. Like Jeff said, anyone working on
6.0 stuff can just keep it in a private branch a little longer.
-Jon
On
I agree that it doesn’t make sense to branch if we’re not going to open main
for 6.0.
I think the main argument for opening main is that developers tend to write
code. The best way to keep them from messing up the stable is to give them
someplace else to put it. ;)
But with git it probably
I quick note to my lead developers (those of you with repo privileges)
please hold off on making any pushes until I make a decision on the
current branch situation. I'm thinking it doesn't make sense to have
two identical branches all the way up to the stable release. All this
does is make
10 matches
Mail list logo