[dev] Renaming branch stable/3.0 to dev/3.0 ???

Martin Winter mwinter at opensourcerouting.org
Thu Apr 13 07:18:08 EDT 2017


On 12 Apr 2017, at 18:55, Lou Berger wrote:

> Alternatively create a release/2.0 ...

This would still give the impression that stable/3.0 is a stable 
version…

I rather don’t have stable (or release) in a name until we have 
something
stable.

- Martin

> On April 12, 2017 9:13:02 PM "Martin Winter" 
> <mwinter at opensourcerouting.org> wrote:
>
>> Curious on an opinion here…
>>
>> Our branches on the github seem to be confusing to newcomers. Most
>> people seem
>> to assume stable/3.0 branch (or master) is the one they should be
>> building from
>> for a stable version.
>>
>> I don’t see much we can do about the master (except maybe update 
>> the
>> description
>> to make it clear that this is the most cutting edge version).
>>
>> But I would propose we rename stable/3.0 to dev/3.0 until we get to a
>> more
>> “stable” version of it.
>>
>> I’m also thinking about having some auto-merge of commits from the 
>> 3.0
>> branch
>> into master for the time being (at least for the non-conflicting
>> commits) to
>> keep master up to date.
>>
>> Thoughts?
>>
>> - Martin
>>
>> _______________________________________________
>> dev mailing list
>> dev at lists.frrouting.org
>> https://lists.frrouting.org/listinfo/dev



More information about the dev mailing list