You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tephra.apache.org by Poorna Chandra <po...@apache.org> on 2016/05/10 08:39:12 UTC
Git branching model
Hi,
We were using git-flow branching model in Tephra before Apache. When
setting up the new git repository for Apache Tephra, James suggested we
move to a simpler master model without develop branch. I don't see a big
advantage of continuing with the current approach of having master track
only the release commits, since we end up keeping the release branches and
tags anyway.
If no one has objections to this then we can move to the simpler master
model and drop develop branch.
Thanks,
Poorna.
Re: Git branching model
Posted by Poorna Chandra <po...@apache.org>.
Filed a JIRA to make master the default branch in git -
https://issues.apache.org/jira/browse/INFRA-12017
Poorna.
On Wed, May 11, 2016 at 11:39 AM, Poorna Chandra <po...@apache.org> wrote:
> Since there are no objections, we'll move to the simpler master model and
> drop the develop branch.
>
> Thanks,
> Poorna.
>
>
> On Tue, May 10, 2016 at 1:49 AM, Henry Saputra <he...@gmail.com>
> wrote:
>
>> +1
>>
>> It will be easier to just maintain master and release branches for Apache
>> projects.
>>
>> - Henry
>>
>> On Tue, May 10, 2016 at 1:39 AM, Poorna Chandra <po...@apache.org>
>> wrote:
>>
>> > Hi,
>> >
>> > We were using git-flow branching model in Tephra before Apache. When
>> > setting up the new git repository for Apache Tephra, James suggested we
>> > move to a simpler master model without develop branch. I don't see a big
>> > advantage of continuing with the current approach of having master track
>> > only the release commits, since we end up keeping the release branches
>> and
>> > tags anyway.
>> >
>> > If no one has objections to this then we can move to the simpler master
>> > model and drop develop branch.
>> >
>> > Thanks,
>> > Poorna.
>> >
>>
>
>
Re: Git branching model
Posted by Poorna Chandra <po...@apache.org>.
Since there are no objections, we'll move to the simpler master model and
drop the develop branch.
Thanks,
Poorna.
On Tue, May 10, 2016 at 1:49 AM, Henry Saputra <he...@gmail.com>
wrote:
> +1
>
> It will be easier to just maintain master and release branches for Apache
> projects.
>
> - Henry
>
> On Tue, May 10, 2016 at 1:39 AM, Poorna Chandra <po...@apache.org> wrote:
>
> > Hi,
> >
> > We were using git-flow branching model in Tephra before Apache. When
> > setting up the new git repository for Apache Tephra, James suggested we
> > move to a simpler master model without develop branch. I don't see a big
> > advantage of continuing with the current approach of having master track
> > only the release commits, since we end up keeping the release branches
> and
> > tags anyway.
> >
> > If no one has objections to this then we can move to the simpler master
> > model and drop develop branch.
> >
> > Thanks,
> > Poorna.
> >
>
Re: Git branching model
Posted by Henry Saputra <he...@gmail.com>.
+1
It will be easier to just maintain master and release branches for Apache
projects.
- Henry
On Tue, May 10, 2016 at 1:39 AM, Poorna Chandra <po...@apache.org> wrote:
> Hi,
>
> We were using git-flow branching model in Tephra before Apache. When
> setting up the new git repository for Apache Tephra, James suggested we
> move to a simpler master model without develop branch. I don't see a big
> advantage of continuing with the current approach of having master track
> only the release commits, since we end up keeping the release branches and
> tags anyway.
>
> If no one has objections to this then we can move to the simpler master
> model and drop develop branch.
>
> Thanks,
> Poorna.
>