We are starting the work on Apache Camel 3. We are working at multiple levels to improve Camel and introduce new features.
The first work has actually started by Guillaume Nodet in the start of October, where he jump started by cleaning up the codebase, removed deprecated code and components, improving the routing engine and other internals in the core. His work is published on the sandbox/3.x branch. We plan to use his work as the baseline for the actual Camel 3. Andrea has helped by aligning this branch with all the changes from the master branch (2.x) so its fully up to date. The intention is to switch over the sandbox/3.x branch as the new master branch, so we call can start working on that branch and being able to add new features, components etc. (as always) for Camel 3.
For 2.x users we will create a 2.x branch where we plan to do 1 or 2 more last 2.x releases, eg 2.24 and 2.25, before 3.0 is ready and released.
Here in the beginning of the Camel 3 work is to continue the work from Guillaume Nodet and finish up the cleanup of the codebase, modularize the camel-core, etc.
We invite community users and any Camel committers and developers who has interest to help with the Camel 3 work. We have talked about doing a number of milestone releases of 3.x that can help give feedback to u quicker and faster. For example any Camel users of 2.x can try to upgrade and use the 3.0 milestone releases to report back their findings.
Camel 3 is planned to be a time boxed release to avoid it dragging out “forever”, and with a bit of good luck we will have Camel 3 released after the summer 2019.
We will keep the community posted on the progress, and as always we love
contributions and any feedback you may have.
The 3-humped Camel is coming in 2019 ;)
Published on Java Code Geeks with permission by Claus Ibsen, partner at our JCG program. See the original article here: Work on Apache Camel 3 has finally started Opinions expressed by Java Code Geeks contributors are their own. |
