Hi JB,

Think one key point for this ambition is to be able to ensure releases
don't depend on a single man (whatever his quality is ;)).
Checking on apache index it seems around 3-4 PMC are active (I can be wrong
since I don't follow the list accurately from very long so happy if it is
more), what about having planned (each two months?) releases and rotating
in the PMC for the releases? The big advantage is that it enables fallbacks
when needed and avoids to put pressure on a single man which is also a
positive sign community wide and for the project IMHO. It can also enable
to highlight that some points can be too hard and needs some love (not sure
if accurate but thinking out loud it can be to split the repo in smaller
ones to make releases easier, to make the build parallelizable, to automate
dist upload, to automate site update with a "main" or script, etc...).

Hope it makes some sense.

Just my 2cts indeed.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>


Le mer. 7 oct. 2020 à 06:13, Jean-Baptiste Onofre <j...@nanthrax.net> a
écrit :

> Hi guys,
>
> I would like to be back on more regular/stable release cycle for Karaf.
> Again, I was a little bit too ambitious in release content and it means
> that releases have been postponed several times.
> That’s not good and we should have some more stable/regular: my bad.
>
> So, now, the release should be more driven by time more than content.
> Starting from now, I will try to keep regular releases.
> It’s very important in the new Karaf direction, given the opportunity to
> include more regularly coming features.
>
> Thanks,
> Regards
> JB

Reply via email to