Am 01.02.13 08:44 schrieb "Claus Ibsen" unter <claus.ib...@gmail.com>:
>Hi > >We released 2.10.3 in the middle of December 2012. > >Since this release we have resolved 78 tickets in JIRA. >https://issues.apache.org/jira/browse/CAMEL/fixforversion/12323558#selecte >dTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel > >I think its tine we cut a 2.10.4 release for the community. >For example it fixes the FTP issue a number of users had upgrading to >2.10.3. > >And we are also waiting for Karaf 2.3.1 to be released before we can >cut Camel 2.11.0, >and that release is hold back due a new Aries Blueprint release is to >be cut for fix a big issue. > >So I think we should use this time to cut a 2.10.4 release. > > >We could also consider Camel 2.9.6 but that branch is 1+ year now, so >IMHO its okay that >we settle down a bit and cut patch releases less frequent. > >However my priority would be to get a new 2.10.x patch release out. > >Any thoughts? +1 I just noticed that currently the 2.10.x branch doesn't compile @ camel-blueprint because of CAMEL-6023 fix being (as is) backported. I think the problem is because on this brunch we're still on OSGi 4.2.0. Babak > > >-- >Claus Ibsen >----------------- >Red Hat, Inc. >FuseSource is now part of Red Hat >Email: cib...@redhat.com >Web: http://fusesource.com >Twitter: davsclaus >Blog: http://davsclaus.com >Author of Camel in Action: http://www.manning.com/ibsen
