On May 15, 2013, at 3:10 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Its been 2.5 months ago we released 2.10.4. > > I think we should start considering doing a 2.10.5 release. Which is > also needed by the ServiceMix team for any new 4.5.x releases of > theirs.
Yep. I was hoping to start discussing this last week, but the CXF release definitely took more "effort" than I had hoped. :-( Anyway, with the CXF upgrade and all the other fixes, definitely worth doing. > And since we migrated to git, it would be a good idea to cut a release > to ensure that we can still do releases, and that we iron out any > issues we encounter after the svn -> git change. The change to svn -> git definitely is going to require some updates to poms, updates to the release docs, etc… I know I haven't used the maven-release-plugin with a git repo before. Has anyone here done it? Any gotchas we should be aware of? On a related note… in the git repo, we have a branch just called "2.11.x" for the 2.11.x fixes, but the 2.10.x branch is called "camel-2.10.x". Should we consider renaming one of them to be consistent? (I'd personally prefer the 2.10.x syntax, but ALL the old branches are camel-#.#.x) We should decide on that before the release so the poms get the right branch in them. -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
