Hi Yeah I would like to be able to more quickly cut a RC or Milestone release of an upcoming release.
But it's the 72h voting delay that annoys me the most. We should check up on ASF policy if there can be quicker releases for example for milestone releases or something like that. And on top of that we have separated spring boot so it would also take effort into making camel-spring-boot ready for release as RC1 and cut that too. On Sun, Feb 2, 2020 at 2:39 PM Luca Burgazzoli <lburgazz...@gmail.com> wrote: > > hey, what about having a 3.1 RCx in any case even if we have some open > issues ? > given the amount of changes we have in 3.1, having an RC could help > sub-projects like camel-quarkus and camel-k to start adapting > > --- > Luca Burgazzoli > > > On Thu, Jan 30, 2020 at 2:14 PM Claus Ibsen <claus.ib...@gmail.com> wrote: > > > Hi > > > > We also have to look ad fix > > > > JDK 11 compiling error and test errors that may be there > > > > OSGi blueprint issue (Andrea created a JIRA) > > > > > > On Mon, Jan 27, 2020 at 11:18 AM Claus Ibsen <claus.ib...@gmail.com> > > wrote: > > > > > > Hi > > > > > > I just wanted to start the process of getting closer to Camel 3.1 > > release. > > > Despite 3.0 was released only a while back, then we have made great > > > progress on 3.1 that is important to get in the hands of the Camel > > > users. And for Camel users that migrate to 3.x can then skip 3.0 and > > > go straight to 3.1. > > > > > > I am working on some further optimizations in the core for 3.1, and I > > > hope to find time to share more details in a blog. > > > > > > However to get the other work (high level) done and ready for 3.1, > > > then lets discuss them here on the @dev mailing list. > > > > > > On top of my head we have to do > > > > > > 1) > > > Finish the separation of camel-spring-boot (there are some tools that > > > update docs and generate component list) that needs to be completed. > > > > > > 2) > > > Generate source code configurer for data formats and languages > > > > > > 3) > > > The component configuration fluent builder (would be nice) > > > > > > 4) > > > More camel AWS SDK2 components > > > > > > 5) > > > Camel Main to plugin the new lightweight XML route parser/loader (for > > > example auto discover on classpath the JAR and use it instead of JAXB) > > > > > > There are other things of course, but these are the bigger high level > > > things I could remember. > > > > > > The usual work with new components, examples, other improvements is of > > > course also ongoing. > > > > > > Lets see if we can get this done and release Camel 3.1 in February. > > > > > > > > > > > > > > > -- > > > 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 > > -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
