Hi, Are we getting closer to build a 2.19.0 release? I would volunteer for creating the release, just wanted to check when would be a good time to do so.
Thanks, Gregor On Wed, Mar 15, 2017 at 9:29 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > Just wanted to bring up that we are closing in on a good time for > doing a new release. > > For example in mid April it would be around 6 months since the last > 2.18.0 release. > > Therefore we should start closing down and fixing bugs, and make sure > the CI servers and tests are in good shape. > This morning we have fixed a number of recent test failures and are > down to only 1 test failure now. > > > > On Mon, Jan 16, 2017 at 10:28 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: >> Hi >> >> There is a bunch of stuff which we can/should have on the roadmap to >> complete for the Camel 2.19 release. >> >> Here is on top of my head >> >> 1) >> Finish migrating the wiki documentation to adoc files. I think its >> most of the EIP patterns that are missing. There is a basic list of >> EIPs here: >> https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc >> >> 2) >> Generate documentation and website. Maybe documentation first and then >> we come up with a modern website later - when we have a new logo as >> well. >> >> 3) >> Mark more stuff to @deprecate so we dont drag them into Camel 3.0. >> This is both components / and other artifacts. >> And as well the camel-core APIs where there is maybe more we can deprecate. >> For example the old stuff that was created prior to the component docs >> we do now with the apt plugin at build time instead of this old code >> with runtime that dont really pan out anyway. >> >> 4) >> Move spring-boot starters into the platforms folder. There is a ticket >> about this. >> >> 5) >> More improvements to spring boot auto configuration. We have a bunch >> of tickets on that. >> >> 6) >> Look at the health check API and see if there is something we can get >> started on. >> Possible some API to integrate with spring boot actuators (when using >> SB) and allow each component to provide their own checks so they can >> be implemented ad-hoc. There is a ticket about this. >> >> 7) >> Possible some more teaks to camel-catalog based on feedback from IDEA >> plugin and the maven validate goal. >> >> 8) >> That CDI JEE transaction PR on github. >> Ideally we would have had a transaction API in camel-core and then one >> impl for camel-spring, and then another for camel-cdi-jee. But that >> may require too much work. >> >> 9) >> Work on the Java 8 DSL such as get more community feedback, and then >> resolve the TODOs with the documentation updates and look into other >> areas where the API can benefit from Java 8 lambdas and whatnot. I >> dont think we have a ticket about this. >> >> 10) >> Karaf users may want to improve/finish up the camel-test-karaf module >> so its more usable and end users can use it to test integration tests >> with Camel and Karaf. >> >> 11) >> Introduce Camel Connectors (more about this later) >> >> >> Anything else? >> >> >> >> >> >> -- >> Claus Ibsen >> ----------------- >> http://davsclaus.com @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
