Hi,

Just updating the repo to work on it. I will ping Andrea to move forward on 
this.

Regards
JB

> Le 26 mars 2020 à 17:17, Andrea Cosentino <anco...@gmail.com> a écrit :
> 
> for the camel-karaf repo I mean :-)
> 
> Il giorno gio 26 mar 2020 alle ore 17:17 Andrea Cosentino <anco...@gmail.com>
> ha scritto:
> 
>> And Gregor, this time we'll try the dryRun of the release ahead of time to
>> be sure everything works fine :-)
>> 
>> Thanks
>> 
>> Il giorno gio 26 mar 2020 alle ore 17:16 Claus Ibsen <
>> claus.ib...@gmail.com> ha scritto:
>> 
>>> Hi
>>> 
>>> Okay I think it would be good to see if we at end of next week could
>>> be ready to cut the Camel 3.2.0 release.
>>> 
>>> Gregor is you are listening would you have time to help cut the
>>> release around that time?
>>> 
>>> On Wed, Mar 25, 2020 at 7:10 PM Claus Ibsen <claus.ib...@gmail.com>
>>> wrote:
>>>> 
>>>> Hi
>>>> 
>>>> Its been a week so lets re-cap a summary of where we are on the 3.2
>>> roadmap.
>>>> Comments inline
>>>> 
>>>> On Tue, Mar 17, 2020 at 9:42 AM Claus Ibsen <claus.ib...@gmail.com>
>>> wrote:
>>>>> 
>>>>> 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
>>>>> 
>>>> 
>>>> Work in progress. We would likely get the last bits done this week.
>>>> 
>>>> 
>>>>> 2)
>>>>> Separate model and runtime
>>>>> 
>>>> 
>>>> gnodet has been doing some work on this and pushed a bunch of commits
>>> today.
>>>> 
>>>>> 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.
>>>>> 
>>>> 
>>>> gnodet has been doing some work on this and pushed a bunch of commits
>>> today.
>>>> 
>>>>> 4)
>>>>> Optimize camel-core some more
>>>>> 
>>>> 
>>>> i was on a path to do some more optimizatations but hit a corner, so
>>>> the work sits in a local branch.
>>>> 
>>>> 
>>>>> 5)
>>>>> Build process of documentation and restructure improvements (david
>>> jenks)
>>>>> 
>>>> 
>>>> David is working hard on this.
>>>> 
>>>>> 6)
>>>>> Unify and make it easier to do custom component configuration across
>>>>> runtimes (CAMEL-14672)
>>>>> 
>>>> 
>>>> Work not started
>>>> 
>>>>> 7)
>>>>> Simplify rest-dsl configuration to be only one configuration
>>> (CAMEL-13844)
>>>>> 
>>>> 
>>>> Done
>>>> 
>>>>> 8)
>>>>> Add missing option descriptions (reported by SB but can be general -
>>>>> CAMEL-14565)
>>>>> 
>>>> 
>>>> Work not started
>>>> 
>>>>> 
>>>>> Any thoughts?
>>>>> 
>>>> 
>>>> Also for the camel-karaf sub project we need to add it to the website
>>>> as a menu option just like the others.
>>>> And also have it in the components list of the components it support
>>>> (like for spring boot etc).
>>>> 
>>>> 
>>>>> --
>>>>> 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
>>> 
>> 

Reply via email to