[OpenSIPS-Devel] Repository branches

[Liviu Chircu]

Hi, Dan!

Development for 3.0 has ended and the beta phase has begun, so why not 
signify this by forking its own branch?  We then make use of tags to 
mark the progression of the 3.0 release.

Having to cherry-pick each commit one more time seems a lot less of a 
problem than the potential confusion caused by announcing that 3.0 has 
progressed into beta phase while we are still asking the community to 
work with the in-development-but-feature-freezed "master" branch?

Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com

On 17.04.2019 09:04, Dan Pascu wrote:
> I noticed that a 3.0 branch was already created. I believe it would make our lives easier if this branch is only created when 3.0 is actually released, otherwise every commit in master needs to be duplicated in 3.0. If you just want to prevent unexpected things ending up in 3.0, just institute a feature freeze until release.
>
> --
> Dan
>
>
>
>
>
> _______________________________________________
> Devel mailing list
> Devel at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel