You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Gary Gregory <ga...@gmail.com> on 2016/08/09 15:59:00 UTC
[RNG] Rename develop branch to master
We should match the rest of Commons and have a master branch instead of
develop IMO.
Gary
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [RNG] Rename develop branch to master
Posted by Emmanuel Bourg <eb...@apache.org>.
Le 9/08/2016 � 18:20, Gilles a �crit :
> No problem changing the layout.
>
> develop -> master
> master -> released
>
> But someone should make the necessary adjustments to the howto
> (with the drawback that the reference therein would become
> fairly confusing).
I renamed the branch, please update your repositories and switch to the
new branch. I'll update the documentation.
Emmanuel Bourg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [RNG] Rename develop branch to master
Posted by Gilles <gi...@harfang.homelinux.org>.
On Tue, 9 Aug 2016 08:59:00 -0700, Gary Gregory wrote:
> We should match the rest of Commons and have a master branch instead
> of
> develop IMO.
>
> Gary
As we already discussed, it's not about the layout, it's about
a development model.
There is a model in "doc/development/development.howto.txt".
E.g. after the initial adjustments and the project repository
becomes stable, I expect that changes are made in a controlled
way, through "feature" branches, to be merged into "develop" (or
"master" whatever) after having left "some time" (TBD) for
reviewer to chime in.
As explained in
http://nvie.com/posts/a-successful-git-branching-model/
it helps keep "develop" clean and "master" super-clean.
No problem changing the layout.
develop -> master
master -> released
But someone should make the necessary adjustments to the howto
(with the drawback that the reference therein would become
fairly confusing).
Regards,
Gilles
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org