On Mon, May 6, 2013 at 12:25 PM, Adolfo Benedetti < [email protected]> wrote:
> Hi Chris, > > Why not use > " > A successful Git branching/releasing model > " like this one[1], with gitflow[2] this process is really easy. > This is supported by the maven-release-plugin[3] as well, > I'm a huge fan of gitflow but it would be a change from current project practices. I wasn't aware of the integration of Maven but I'm going to read up on it since I use git flow on my project and could potentially use it. For Rave, if we move to git we'd do it with as few of changes as required and then evolve from there. But that's just my 2 cents, maybe others would like a larger change. > > > [1]http://nvie.com/posts/a-successful-git-branching-model/ > [2]https://www.atlassian.com/git/workflows#!workflow-gitflow > [3]https://blogs.atlassian.com/2013/04/git-flow-comes-to-java/ > > Cheers, > > Adolfo > > -- > Adolfo Benedetti > > > 2013/5/6 Chris Geer <[email protected]> > > > I know in the past we talked about migrating to git and there was some > > concern about the release process. Camel just migrated to Git this > weekend. > > Maybe we can get some input from them on their release process if people > > are still interested...or maybe we've figured it out already? > > > > Chris > > >
