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 Sat, Feb 24, 2018, 18:34 Jeff Young <jeff@xxxxxxxxx
<mailto:jeff@xxxxxxxxx>> wrote:
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 doesn’t make that much difference. People
can commit to their own repos.
Cheers,
Jeff.
> On 24 Feb 2018, at 23:30, Wayne Stambaugh <stambaughw@xxxxxxxxx
<mailto:stambaughw@xxxxxxxxx>> wrote:
>
> 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 more work for me without any
tangible benefit. I think we should continue developing version 5
in the development repo until the stable 5 release and then branch.
Can anyone think of a reason not to do this?
>
> Cheers,
>
> Wayne
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
<mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
<mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
