I wonder if we can just get 2.0 out pretty quickly? Removing the generics is a biggie - but once thats done and we hammer on it a bit & tune it; am not sure how long its gonna take us to get 2.0 out the door.
We typically do a new release every few months; so for new features - we can just roll them all into 2.0 can't we? If we just focus on the possible-API-changing stuff first and get that all sorted ASAP we can just ship 2.0 whenever we're happy with it? 2008/11/6 Claus Ibsen <[EMAIL PROTECTED]>: > Hi > > There has been great activity on the Camel after the 1.5 release - really > great. > > But I am wondering if we should push so many of the new features as well into > Camel 1.5.1? > > Do we want to keep maintaining all the new features and code in the 1.x > branch as well? I would like to reconsider what we add to 1.5. Keeping it for > must have features and bug fixes would be more correct IMHO. > > > We should also have the 1.5.1 and 2.0 release "work in progress" pages as > well, so we remember to update on the way. I will add them right now. > > > And please also take the 15 min. to add/modify the wiki documentation as > well. Would be lovely with a checkbox in JIRA you could tick off when you > have fixed the wiki documentation as well ;) Sorry I am just pushing for > documentation as well, as it is a must have to keep the learning curve lower > and motivate new users to use Camel. > > > Med venlig hilsen > > Claus Ibsen > ...................................... > Silverbullet > Skovsgårdsvænget 21 > 8362 Hørning > Tlf. +45 2962 7576 > Web: www.silverbullet.dk > > -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/
