Just in case it help, in Marmotta we follow Giflow with very good results:
http://marmotta.apache.org/development#Source_code Further reading: http://nvie.com/posts/a-successful-git-branching-model/ http://www.atlassian.com/git/workflows#!workflow-gitflow Hope that helps. On 26/11/14 17:35, Tony Kurc wrote:
I wanted to kick off a discussion about workflow in git. There are a lot of techniques in git for working effectively as a team, managing several product versions at once, and for branching and merging code back in. It looks like several other apache projects have guides for their team conventions, such as Deltaspike [1] and Accumulo [2], I think it would be prudent to work on some conventions for NiFi. I've used several styles, one of which works well for other projects I've worked on is called gitflow [3]. I like the concepts of gitflow, but I really don't like depending on maven plugins to execute the conventions. I'd be in favor of something like gitflow, not sure if others had opinions. Tony [1]https://deltaspike.apache.org/suggested-git-workflows.html [2] https://accumulo.apache.org/git.html [3] https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow/
-- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 660 2747 925 e: [email protected] w: http://redlink.co
