Yes, I would be available for cutting the release candidate, but it would be not before the weekend of August 24. Does that work for everyone?
Thanks, Gregor On Sat, Aug 10, 2019, 2:33 PM Andrea Cosentino <[email protected]> wrote: > +1 for release candidate 1. > > Gregor are you able to cut the RC eventually? > > Il sab 10 ago 2019, 15:14 Claus Ibsen <[email protected]> ha scritto: > > > Camel 3.0 Release Candidate 1 > > ============================ > > > > I think its time we should close down on the Camel 3.0 release > > and get out first release candidate out. > > > > The CI server has been looking good lately, we had a few bumps the > > last couple of builds due some new changes. But the next build is > > expected to pass > > https://builds.apache.org/job/Camel/job/master/ > > > > > > > > Since the milestone 4 release we have done a number of noteworthy > > improvements: > > > > 1) > > Renamed components to use normalised names, eg http4 -> http, quartz2 > > -> quartz, etc. > > This gives us a "fresh start" on Camel 3. > > > > 2) > > Introduced JUnit 5 support with the new camel-test-junit5 (more work to > > come). > > > > 3) > > Improved properties component to by default work better in > > container/cloud's where > > ENV variables can override configurations. > > > > 4) > > You can now configure MDC logging to propagste more or all keys by > > patterns. > > > > 5) > > Mock endpoints will now fail fast on first arrived message that fails > > an expecations. > > Beforehand they may on fail after assertion timeout. > > > > 6) > > Fixed an issue with auto configuring Map types in > > application.properties with Camel Spring Boot > > > > 6) > > Intercept send to endpoint can now invoke an after processor that > > allows to do before/after processing. > > > > 7) > > Testing with advice with now support advicing onException and > interceptors. > > > > 8) > > Added new tracer implementation > > > > > > In addition there are other changes and bug fixes, new components, > > etc. And we had some API changes such as deprecating the OUT message > > on Exchange (use getMessage), and the attachment API was externalised > > to camel-attachments etc. So the modularisation of camel-core was > > further improve a bit. We have also improve startup of Camel to avoid > > doing some try .. catch ignore exceptions. > > > > > > You can find all the JIRA tickets for this release at: > > https://issues.apache.org/jira/projects/CAMEL/versions/12345723 > > > > > > > > > > > > > > > > > > > > -- > > Claus Ibsen > > ----------------- > > http://davsclaus.com @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > >
