On Thursday, 30 July 2015 at 01:29:11 pm -0500, Br. Elijah Schwab, O.Carm wrote:
>
> To clarify then: When the develop branch is in version -{beta,rcx} no
> new features are allowed on the develop branch, only bug fixes. For new
> feature code, a release-x.y branch must be made, then the new feature
> code can be merged into develop?
>
There are two things here. First, I'd say that beta does not
necessarily mean feature freeze, which is what you are describing. If
feature freeze is how we want to define beta, then so be it. In my
professional experience, "feature freeze" is a movable concept depending
on what's cooking at the moment.
Secondly, about branching, I am simply suggesting that until we decide
to work on a change of any type which will NOT go into 4.0, there is no
need to (incur the manpower overhead of a) branch. We don't need to
branch until either we decide to work on something which will NOT go
into 4.0 or enter release candidate status, whichever comes first.
If the development team gets larger, of course, things change, and we
would most likely branch sooner, possibly even before the beta period.
Henry
_______________________________________________
Gregorio-devel mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-devel
