+1 to start Camel 3. I'd be happy to join the development. Let's make it happen by discussion the roadmap first.
Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Dec 11, 2018 at 9:59 PM Andrea Cosentino <ancosen1...@yahoo.com.invalid> wrote: > > Hello Camelers, > > 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. I have 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 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 us 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. > > Over the coming weeks it would be good if we could work on the roadmap and a > rough timetable for Camel 3 so we can sketch out the first set of goals for > the first milestone release and then rinse and repeat for the upcoming > milestone releases. > > We have also talked about letting Camel 3 be a timeboxed release to avoid it > dragging out “forever”. It would be great if we can build and release Camel 3 > within 1 year of development, for example maybe try to aim for a release in > Q3 2019. > > We will keep the community posted on the progress, and as always we love > contribution and any feedback. > > Exciting times ahead! > > Thoughts? > > Claus & Andrea > > -- > Andrea Cosentino > ---------------------------------- > Apache Camel PMC Chair > Apache Karaf Committer > Apache Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd
