Hi Its good if you have the cycles to cut both 2.10 and 2.9. This is really good. Though if we only have cycles for one release, then we should favor 2.10.
I took the liberty of creating 2.10.5 and 2.9.7 versions in JIRA and moved some tickets to these versions. So we have no outstanding tickets for 2.10.4 and 2.9.6. Then Hadrian should have clear-road for cutting these releases. +1 to cut the releases when you can Hadrian. On Tue, Feb 5, 2013 at 4:26 AM, Hadrian Zbarcea <hzbar...@gmail.com> wrote: > For some reason still not clear to me, my mail client didn't get the > original thread started by Claus. That points to consensus that it's time > for a 2.10.4. I started a full build overnight and I am planning to build > the 2.10.4 release later this week, Wed or Thu. > > Regarding 2.9.x, we did decided a while ago to support 2 versions back, > right? So even if we wouldn't need a 2.9.6 release now, it should still be > supported until 2.11.0 is out. However with almost 50 issues fixed, I think > we should get 2.9.6 out the door as well, so I'm planning to release it this > week as well. > > Is there anything you're working on that should make it into 2.10.4 and > 2.9.6? Please shout now. > > Cheers, > Hadrian -- 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
