On Jul 30, 2015 10:56, Henry So Jr. wrote:
> On Thursday, 30 July 2015 at 04:41:17 pm +0200, Élie Roux wrote:
> > Le 30/07/2015 16:29, Henry So Jr. a écrit :
> > > I'll go with the majority on this, but that is a good summary of what
> > > I'm suggesting. I only see a reason to branch when there is more than
> > > one code line to manage.
> >
> > I think both options are valid: branching is more correct on a workflow
> > point of view, but at the same time it's quite useless and will just
> > give more work for no benefit (unless of course somebody starts to work
> > on something that won't appear in 4.0). I admit I tend to prefer not
> > branching at this point, but be ready to branch if the circumstances
> > change... What do you think?
>
> For what it's worth, I agree with this as the guideline.
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?
If so, I am fine with this.
-Br. Elijah
_______________________________________________
Gregorio-devel mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-devel
