Yeah, agreed. Like we even still have the 1.x branch there. No harm in keeping them around IMO.
On Tue, Jan 3, 2012 at 12:17 PM, Daniel Kulp <[email protected]> wrote: > On Saturday, December 31, 2011 7:43:26 PM Christian Müller wrote: > > When we release Camel 2.9.0 (expected in the next days) and start working > > on Camel 2.10, I would like to cut a new release from the camel-2.7.x > > branch which will be in my opinion the last Camel 2.7 release because we > > discussed to support the two privios relases which then are Camel 2.8 and > > 2.9. > > > > What do you think? > > I'm OK with dropping planned support for 2.7.x. However, we should keep > the > branch in place and the Jenkins builds setup (maybe disabled, but really, > if > there are no svn commits on the branch, they shouldn't trigger) so that if > we > do need to spin another build for any reason, we can. > > > > -- > Daniel Kulp > [email protected] - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com > -- Cheers, Jon --------------- FuseSource Email: [email protected] Web: fusesource.com Twitter: jon_anstey Blog: http://janstey.blogspot.com Author of Camel in Action: http://manning.com/ibsen
