Re: Extend LTS concept to Camel K
Hey Andrea, I somehow understood that only PMC could perform releases. Could you please clarify if that is correct? Thanks, Pasquale. On Wed, Sep 14, 2022 at 2:59 PM Andrea Cosentino wrote: > Thanks for the help, > > I think you could try to release yourself with the next 1.10.x or 1.11.0. > > https://github.com/apache/camel-k/blob/main/release.adoc > > Here there is a step by step guide I've been trying to improve. > > > > Il giorno mer 14 set 2022 alle ore 09:41 Tadayoshi Sato < > sato.tadayo...@gmail.com> ha scritto: > > > Hi Andrea, > > > > > > > It makes sense, we need to find a way to rotate the release manager, > > > because especially post-release steps are time-consuming. > > > > > > > I can volunteer for the release manager for Camel K. Let me know how I > can > > help. > > > > On Tue, Sep 13, 2022 at 9:10 PM Andrea Cosentino > > wrote: > > > > > 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 > > > > 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 > > > > > > > > > > > > > -- > > Tadayoshi Sato > > >
Re: Extend LTS concept to Camel K
Thanks for the help, I think you could try to release yourself with the next 1.10.x or 1.11.0. https://github.com/apache/camel-k/blob/main/release.adoc Here there is a step by step guide I've been trying to improve. Il giorno mer 14 set 2022 alle ore 09:41 Tadayoshi Sato < sato.tadayo...@gmail.com> ha scritto: > Hi Andrea, > > > > It makes sense, we need to find a way to rotate the release manager, > > because especially post-release steps are time-consuming. > > > > I can volunteer for the release manager for Camel K. Let me know how I can > help. > > On Tue, Sep 13, 2022 at 9:10 PM Andrea Cosentino > wrote: > > > 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 > > > 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 > > > > > > > > -- > Tadayoshi Sato >
Re: Extend LTS concept to Camel K
+1. I think it would be good to have an LTS version of Camel K. Kind regards On Wed, Sep 14, 2022 at 9:41 AM Tadayoshi Sato wrote: > Hi Andrea, > > > > It makes sense, we need to find a way to rotate the release manager, > > because especially post-release steps are time-consuming. > > > > I can volunteer for the release manager for Camel K. Let me know how I can > help. > > On Tue, Sep 13, 2022 at 9:10 PM Andrea Cosentino > wrote: > > > 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 > > > 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 > > > > > > > > -- > Tadayoshi Sato > -- Otavio R. Piske http://orpiske.net
Re: [camel] branch main updated: Remove redundant vertx-web-client-version property as it was only required to work around an issue in Vert.x 4.3.2
I think this needs to be backported to 3.18.x too. This was creating
problems in camel k runtime testing while trying to align to 3.18.1 and
camel quarkus related release. So I suppose we'll have problem with 3.18.2
too and CQ release
Il mer 14 set 2022, 11:58 ha scritto:
> This is an automated email from the ASF dual-hosted git repository.
>
> jamesnetherton pushed a commit to branch main
> in repository https://gitbox.apache.org/repos/asf/camel.git
>
>
> The following commit(s) were added to refs/heads/main by this push:
> new 89554d78552 Remove redundant vertx-web-client-version property as
> it was only required to work around an issue in Vert.x 4.3.2
> 89554d78552 is described below
>
> commit 89554d7855279b2fa515114e96b8f3a07785b047
> Author: James Netherton
> AuthorDate: Wed Sep 14 10:57:15 2022 +0100
>
> Remove redundant vertx-web-client-version property as it was only
> required to work around an issue in Vert.x 4.3.2
> ---
> camel-dependencies/pom.xml | 1 -
> components/camel-knative/camel-knative-http/pom.xml | 2 +-
> components/camel-vertx/camel-vertx-http/pom.xml | 2 +-
> parent/pom.xml | 1 -
> 4 files changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/camel-dependencies/pom.xml b/camel-dependencies/pom.xml
> index fc66d83ee2a..50b663a6cb8 100644
> --- a/camel-dependencies/pom.xml
> +++ b/camel-dependencies/pom.xml
> @@ -532,7 +532,6 @@
> 3.1
> 2.3
> 4.3.3
> -4.3.3
> 0.7
> 0.8.0
> 3.6.0
> diff --git a/components/camel-knative/camel-knative-http/pom.xml
> b/components/camel-knative/camel-knative-http/pom.xml
> index ec5c2ea3975..7d83a7e2bec 100644
> --- a/components/camel-knative/camel-knative-http/pom.xml
> +++ b/components/camel-knative/camel-knative-http/pom.xml
> @@ -50,7 +50,7 @@
>
> io.vertx
> vertx-web-client
> -${vertx-web-client-version}
> +${vertx-version}
>
>
> io.vertx
> diff --git a/components/camel-vertx/camel-vertx-http/pom.xml
> b/components/camel-vertx/camel-vertx-http/pom.xml
> index 7e2983df2e1..983ca276f13 100644
> --- a/components/camel-vertx/camel-vertx-http/pom.xml
> +++ b/components/camel-vertx/camel-vertx-http/pom.xml
> @@ -46,7 +46,7 @@
>
> io.vertx
> vertx-web-client
> -${vertx-web-client-version}
> +${vertx-version}
>
>
>
> diff --git a/parent/pom.xml b/parent/pom.xml
> index bb577ff5de8..3f8ddee5c16 100644
> --- a/parent/pom.xml
> +++ b/parent/pom.xml
> @@ -519,7 +519,6 @@
> 3.1
> 2.3
> 4.3.3
> -4.3.3
> 0.7
> 3.6.0
> 0.8.0
>
>
Re: Extend LTS concept to Camel K
Hi Andrea, > It makes sense, we need to find a way to rotate the release manager, > because especially post-release steps are time-consuming. > I can volunteer for the release manager for Camel K. Let me know how I can help. On Tue, Sep 13, 2022 at 9:10 PM Andrea Cosentino wrote: > 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 > > 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 > > > -- Tadayoshi Sato
