Yeah, I don't like the idea of too many features going into the bug fix branch... I'd say don't do it unless there is a good reason. Well, we don't really have any rules for what goes into one of these branches so it is probably not so clear :)
We should really keep the docs up to date though when merging improvements/features. I'll update the docs for CAMEL-4290, CAMEL-4297, CAMEL-4382 since I originally committed them but there still may be more that need to be updated. On Tue, Sep 20, 2011 at 3:41 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > Dan what is the reason why you backport so many commits to 2.8.2 from 2.9? > > The "problem" is that its a lot of new features, non trivial bug fixes > and whatnot. > People then may not have a safe upgrade from 2.8.0 / 2.8.1 to 2.8.2 > because of the "big difference". > People is more prepared for a little trouble when doing 2.8.0 to 2.9.0 > upgrade. But not for an upgrade in 2.8.x branch. > > Also for new features and whatnot we update the documentation to > indicate eg *Camel 2.9* that > this is a new feature in that version. These documentation changes is > not part of the SVN and thus > you lose this, and cannot keep the documentation <-> source code in sync. > > > > > -- > Claus Ibsen > ----------------- > FuseSource > Email: cib...@fusesource.com > Web: http://fusesource.com > Twitter: davsclaus, fusenews > Blog: http://davsclaus.blogspot.com/ > Author of Camel in Action: http://www.manning.com/ibsen/ > -- Cheers, Jon --------------- FuseSource Email: j...@fusesource.com Web: fusesource.com Twitter: jon_anstey Blog: http://janstey.blogspot.com Author of Camel in Action: http://manning.com/ibsen
