accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Elser <>
Subject Re: [PROPOSAL] 1.7/2.0 branches and git workflow change
Date Tue, 07 Oct 2014 01:19:44 GMT
Christopher wrote:
>> What purpose does the master branch serve if it's just the same as the last
>> >  major release tag?
>> >
>> >
> I think Josh had some specific opinions on this, but the general idea from
> what I understood was that master is supposed to be stable...
> representative of the latest, most modern release, because it's what a new
> contributor would expect to fork to create a patch. That's hard to do if
> the goalpost is moving a lot, and it makes feature merges more complicated,
> since contributors have to rebase or merge themselves in order to create a
> patch that merges cleanly. Having a stable master makes it very easy to
> contribute to the most recent release.

No, I don't really care for a stable-only master (I think I diverge from 
the git-flow model in that regard). I like master to just be a 
"commits-go-here" area more than anything.

View raw message