Hi Eli, Benoit linked to a variant of it in the beginning of this thread. There's a lot to
like about it, and most of it is very similar to the workflow we're converging on in this
project. The big difference is that in git-flow the HEAD of "master" is always the latest
tagged release, and that "develop" is where the day-to-day completed work lands.
Personally I don't think I would coerce CouchDB into the nominal git-flow shape, but I thought
I'd note the similarities in case others find the tooling really appealing. Cheers,
Adam
On Nov 1, 2012, at 8:54 PM, "Eli Stevens (Gmail)" <wickedgrey@gmail.com> wrote:
> Are the committers familiar with git-flow?
>
> http://nvie.com/posts/a-successful-git-branching-model/
> https://github.com/nvie/gitflow
>
> Having used it at work for closed-source projects, I recommend it as
> the script support is nice, and it provides a decent branching model
> that "just works." While we don't use github's automatic merges, it
> does play nicely with the github pull request system (perhaps less
> relevant for an apache project).
>
> I don't see any reason why it wouldn't work just as well for open
> source projects.
>
> Cheers,
> Eli
|