Can you please push a branch? So we can work together next week? Il gio 19 mar 2020, 18:29 Jean-Baptiste Onofre <[email protected]> ha scritto:
> Hi, > > From my side, I started to work on "camel-karat" isolation. > > Regards > JB > > > Le 19 mars 2020 à 09:55, Luca Burgazzoli <[email protected]> a > écrit : > > > > I've started working on > https://issues.apache.org/jira/browse/CAMEL-14738, > > hope to have it ready by the end of the week. > > > > --- > > Luca Burgazzoli > > > > > > On Tue, Mar 17, 2020 at 10:33 AM Andrea Cosentino <[email protected]> > wrote: > > > >> I think we need to describe better the release process, so we can > rotate a > >> bit. > >> > >> Il giorno mar 17 mar 2020 alle ore 09:42 Claus Ibsen < > >> [email protected]> > >> ha scritto: > >> > >>> Hi > >>> > >>> We have 2-3 weeks IMHO to get the last bits done for the 3.2.0 release. > >>> Camel 3.2 is ETA for April 2020. > >>> > >>> The roadmap are currently (not limited to) > >>> > >>> 1) > >>> Move karaf to camel-karaf as sub-project > >>> > >>> 2) > >>> Separate model and runtime > >>> > >>> 3) > >>> Reduce footprint of Camel in static/closed-world runtimes such as > >>> graalvm, camel-quarkus, camel-k - such as the immutable camel context, > >>> and reduce classes on classpath for dead-code elimination and what > >>> else. > >>> > >>> 4) > >>> Optimize camel-core some more > >>> > >>> 5) > >>> Build process of documentation and restructure improvements (david > jenks) > >>> > >>> 6) > >>> Unify and make it easier to do custom component configuration across > >>> runtimes (CAMEL-14672) > >>> > >>> 7) > >>> Simplify rest-dsl configuration to be only one configuration > >> (CAMEL-13844) > >>> > >>> 8) > >>> Add missing option descriptions (reported by SB but can be general - > >>> CAMEL-14565) > >>> > >>> > >>> Any thoughts? > >>> > >>> -- > >>> Claus Ibsen > >>> ----------------- > >>> http://davsclaus.com @davsclaus > >>> Camel in Action 2: https://www.manning.com/ibsen2 > >>> > >> > >
