I assume somebody will take the stab to build Camel 2.10.0 in the next 4 - 6 weeks (if not, I will do it to be right here ;-) ). At present we have 276 issues assigned to this version [1]. 209 are already fixed.
I think this is a good time to discuss whether the next version will be 2.11.0 or 3.0.0. *IF* the next version will be 3.0.0, we should have in mind that this version: 1) Probably needs more time than our normal 3 month schedule for a new minor version 2) Will break backwards compatibility and we want to provide a migration path for our users where possible. Because of this I would like to know: - Do we have to deprecate some more API's which we plan to drop in Camel 3.0.0? - Do we have to add some new API's stubs so that our users can start to migrate to the new API in Camel 2.10.0 (if possible)? Because of this I would like to see the following issues includes in Camel 2.10.0: - CAMEL-4955 <https://issues.apache.org/jira/browse/CAMEL-4955> More and more user want to run Camel with Java 7. If we postpone it to Camel 3.0.0, we are very late with supporting Java 7. Apache Karaf supports Java 7 since version 2.2.3 - available since more than 6 month... - <https://issues.apache.org/jira/browse/CAMEL-4886>CAMEL-4778<https://issues.apache.org/jira/browse/CAMEL-4778>Also more and more user would like to start using Spring 3.1., some did it already. I think we should start to support Spring 3.1. officially in Camel 2.10.0. And if the next version will not be Camel 3.0.0, I'm wondering for what we are waiting... ;o) [1] https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=fixVersion+%3D+%222.10.0%22+AND+project+%3D+CAMEL [2] https://issues.apache.org/jira/browse/KARAF-829 Looking for your opinions, Christian
