+1
On Wed, Feb 25, 2009 at 9:08 AM, Hadrian Zbarcea <[email protected]> wrote: > +1 > > I created a 2.0-M1 version in jira. Let's assign the issues we want to > close down in the M1 release and I will cut the release. > > > > On Feb 24, 2009, at 8:08 AM, James Strachan wrote: > >> Agreed - lets get 2.0 out ASAP - while releasing bug fixes in 1.6.1. >> Not sure if we'll ever need a 1.7? >> >> 2009/2/24 Jon Anstey <[email protected]>: >>> >>> +1 on fully compatible 1.6.1 >>> >>> We're getting closer to 2.0 being complete anyways so it makes sense to >>> add >>> new features on one branch only. >>> >>> On Tue, Feb 24, 2009 at 4:52 AM, Claus Ibsen <[email protected]> >>> wrote: >>> >>>> Hi >>>> >>>> I was wondering if we should start a discussion on the scope for the >>>> next Apache Camel 1.x release (notice 1.x branch) >>>> >>>> As we have always done minor versions and no patch releases I was >>>> wondering if we should focus on doing a >>>> - 1.6.1 patch release so end users have a stable release that should >>>> be drop in compatible >>>> - or a new 1.7.0 release >>>> >>>> I am in favor of focusing on a 1.6.1 release. >>>> >>>> Any thoughts? >>>> >>>> >>>> >>>> -- >>>> Claus Ibsen >>>> Apache Camel Committer >>>> >>>> Open Source Integration: http://fusesource.com >>>> Blog: http://davsclaus.blogspot.com/ >>>> >>> >>> >>> >>> -- >>> Cheers, >>> Jon >>> >>> http://janstey.blogspot.com/ >>> >> >> >> >> -- >> James >> ------- >> http://macstrac.blogspot.com/ >> >> Open Source Integration >> http://fusesource.com/ > >
