On Mon, Sep 26, 2011 at 1:29 PM, Christian Schneider <ch...@die-schneider.net> wrote: > Am 26.09.2011 11:04, schrieb Claus Ibsen: >> >> See the survey we did where people comment that they want the API stable. >> http://camel.apache.org/camel-30-roadmap.html (link on top of this page) We >> have not recently put our a survey to ask for feedback in the community if >> they want bigger API changes in the 2.x, that will break backwards >> compatibility. > > Do you really dsitill the community will out of a single comment from the > survey? I believe that there can be many people who want a stable API but > the only reference I found in the survey was one single comment. >
The following five comments refer to keeping Camel stable: #16, #18, #50, #57, and #58 When I go to conferences and talk with existing Camel users, they all say to keep Camel stable as is. Some users who was using Camel 2.0 in its early days, refers to the API changing a bit, and causing upgrades to become harder, longer and to cost more man power and in the end more $$$. >> Neither have this been discussed in the @dev / among the entire Camel >> team. Instead Christian just carried out doing this work as a "rouge soldier >> on a mission". With no intend to stop. This is disrespectful for the >> community, and for other Camel team members. > > I started some threads about possibly problematic changes. For any API > breakage I also had an issues where mainly you commented a lot. I reacted on > change requests. The more problematic changes I posted as patches first and > committed as the dicussion showed an agreement. So please stop saying that I > don´t discuss things. > You did not start any [DISCUSS] up front with the idea of your API changes. You started creating a JIRA ticket to refactor the management code in camel-core. You did this, and disregarded backwards compatibility. When asked why, you said it was on purpose. Then you went on holiday. We restored the backwards compatibility, which means end users can continue using as is, or migrate to the new API as well. You can say we have the best of both worlds now. No API breakings, and there is a new API in place, that do not disrupt anything. Then you continue focusing on the structure 101 diagrams and start refactoring other parts of the core. Instead it would have IMHO been better judgment from you, if you posted on @dev a [DISCUSS] and gave amble time for the entire Camel team to comment. Remember the team is big and diverse. There are people like you and me, who work on Camel on a daily basis. And then there is a majority of team members who work on Camel from time to time. Or only have time to work in their spare time. They are just as equal part of the team, and should be given time to raise their feedback and voice. >> In the start of this year, when we talked about dropping support for JDK5 >> and Spring 2.x, we discussed this on @dev first. >> http://camel.465427.n5.nabble.com/DISCUSS-Dropping-support-for-java-1-5-from-camel-2-7-0-onwards-td3354712.html >> Then we had a vote. And we put out a message to the community ahead of time >> http://camel.apache.org/2011/02/09/camel-270-drops-support-for-java-15.html >> This time, none of this happened. > > The 2.9 release is not out. So we can still tell the community what to watch > out for. > > Christian > > -- > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > Talend Application Integration Division http://www.talend.com > > -- 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/
