Hi Dan Do you care to discuss this?
You keep on backporting non bug fixes, new features and whatnot. People who run Camel in production and they may want to upgrade to 2.8.2 due to a bug. They frankly do not like a lot of changes. As any change in a production system is not desireable. So the gap from 2.8.0, 2.8.1 to 2.8.2 is now very big. This is not desireable. On Tue, Sep 20, 2011 at 8:11 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/ > -- 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/
