Let’s wait for others feedback on the mailing list. 

> Le 7 févr. 2022 à 08:08, Francois Papon <francois.pa...@openobject.fr> a 
> écrit :
> 
> I can manage the creation of the branch and move the code source.
> 
> regards,
> 
> François
> 
>> On 07/02/2022 08:05, Francois Papon wrote:
>> +1, we can use a dedicated branch :)
>> 
>> regards,
>> 
>> Francois
>> 
>>> On 07/02/2022 08:02, Jean-Baptiste Onofre wrote:
>>> Hi,
>>> 
>>> It sounds good to me.
>>> 
>>> The K5 repo is currently on my GitHub:
>>> 
>>> https://github.com/jbonofre/karaf5
>>> 
>>> I propose:
>>> 
>>> 1. To keep main for karaf-4.4.x for now
>>> 2. Fix K4 like assembly on K5 (just have to push some new services)
>>> 3. Push Karaf 5 on K5 branch
>>> 4. Improve documentation on K5 branch to show what’s a service, and so, 
>>> allow anyone to contribute service/distribution
>>> 
>>> ETA: end of this week if no objection.
>>> 
>>> Regards
>>> JB
>>> 
>>> 
>>>> Le 7 févr. 2022 à 07:56, Francois Papon <francois.pa...@openobject.fr> a 
>>>> écrit :
>>>> 
>>>> Hi,
>>>> 
>>>> As we have some users that asking questions about Karaf 5 the next Karaf 
>>>> generation, I think it would be nice to move the current repo to master.
>>>> 
>>>> It could be a good booster if we want to move forward on this for a first 
>>>> RC.
>>>> 
>>>> Thoughts?
>>>> 
>>>> Regards,
>>>> 
>>>> François
>>>> 

Reply via email to