It makes sense, we need to find a way to rotate the release manager, because especially post-release steps are time-consuming.
But in the end it makes sense to follow LTS approach for both camel-k and camel-k-runtime, for the latter until we find a way to integrate the codebase in camel-quarkus directly. Il giorno mar 13 set 2022 alle ore 13:44 Claudio Miranda < clau...@claudius.com.br> ha scritto: > On Tue, Sep 13, 2022 at 7:31 AM Pasquale Congiusti > <pasquale.congiu...@gmail.com> wrote: > > > > I am not sure if this was discussed in the past, but here goes my > proposal > > to officially extend the LTS concept to Camel K releases as well. Since > we > > Sure, the LTS is a good idea for users and developers, +1. > > Camel has the LTS releases, and camel quarkus [1] seems to have a LTS > too, but there is no camel-k-runtime LTS. > In this case the LTS concept would be extended to camel-k-runtime and > sync the Camel K LTS with the camel quarkus/camel LTS releases ? > > 1. https://camel.apache.org/camel-quarkus/next/index.html > > -- > Claudio Miranda > > clau...@claudius.com.br > http://www.claudius.com.br >
