Hi I would like to wait before forking. Camel 2.0 should be developed in the dark fall/winter ;)
I am sure you guys are also busy with the acquisition and what comes in such a scenario. I propose to fork after 1.5 final and then create a 1.x branch for hot fixes. Med venlig hilsen Claus Ibsen ...................................... Silverbullet Skovsgårdsvænget 21 8362 Hørning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: Willem Jiang [mailto:[EMAIL PROTECTED] Sent: 4. september 2008 11:35 To: [email protected] Subject: [SPAM] Re: getting ready for 1.5 and 2.0 How about we fork a 1.x branch , where we can fix the 1.x issues, and the trunk will be 2.0 snapshot. In this way, we can start the 2.x developement right now. Any thoughts? Willem On Thu, Sep 4, 2008 at 5:19 PM, James Strachan <[EMAIL PROTECTED]>wrote: > We've a mighty 122 issues resolved in 1.5 so far... > > http://issues.apache.org/activemq/browse/CAMEL?report=com.atlassian.jira.plugin.system.project:roadmap-panel > > So I think we should start trying to clear up as many of the > bugs/issues in 1.5 ASAP and moving most of the new features back to > 2.0 so we can release it then start turning our attention to getting > 2.0 out. > > I've created a wiki page to summarise the main focus of 2.0 > http://cwiki.apache.org/confluence/display/CAMEL/Camel+2.0+Design > > As always, thoughts most welcome! > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://open.iona.com >
