Re: [VOTE] Release Apache Camel 4.5.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Mar 25, 2024 at 9:04 AM Alexandre Gallice 
wrote:

> +1 (binding)
>
> Nice job and thanks for cutting the release Gregor,
> Alex
>
> On Sun, Mar 24, 2024 at 11:59 AM Andrea Cosentino 
> wrote:
>
> > +1 (binding)
> >
> > Thanks Gregor
> >
> > Il dom 24 mar 2024, 11:59 Claus Ibsen  ha
> scritto:
> >
> > > Hi
> > >
> > > I created a draft blog for whats new in 4.5. Feel free to add more
> > content,
> > > feedback etc in the GH issue
> > > https://github.com/apache/camel-website/pull/1163
> > >
> > >
> > >
> > > On Sun, Mar 24, 2024 at 11:00 AM Gregor Zurowski <
> > gre...@list.zurowski.org
> > > >
> > > wrote:
> > >
> > > > Hi Everyone:
> > > >
> > > > This is a vote to release Apache Camel 4.5.0, a new LTS release with
> > > > 151 new features and improvements.
> > > >
> > > > Release notes:
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12354104=12311211
> > > >
> > > > == Apache Camel 4.5.0 ==
> > > >
> > > > Staging repository:
> > > >
> > https://repository.apache.org/content/repositories/orgapachecamel-1689/
> > > >
> > > > Tarballs:
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1689/org/apache/camel/apache-camel/4.5.0/
> > > >
> > > > Tag: https://github.com/apache/camel/releases/tag/camel-4.5.0
> > > >
> > > > == Apache Camel Spring Boot 4.5.0 ==
> > > >
> > > > Staging repository:
> > > >
> > https://repository.apache.org/content/repositories/orgapachecamel-1690/
> > > >
> > > > Tag:
> > > >
> > >
> >
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.5.0
> > > >
> > > > Please test this release candidate and cast your vote:
> > > > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.5.0
> > > > [ ] -1 Veto the release (provide specific comments)
> > > >
> > > > The vote is open for at least 72 hours.
> > > >
> > > > Thanks,
> > > > Gregor
> > > >
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -
> > > @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >
> >
>

Re: [VOTE] Release Apache Camel 4.0.2

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Fri, Oct 27, 2023 at 11:06 AM Gregor Zurowski 
wrote:

> +1 (binding)
>
> On Mon, Oct 23, 2023 at 10:44 AM Gregor Zurowski
>  wrote:
> >
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 4.0.2, a new patch release with
> > 30 improvements and fixes.
> >
> > Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353661=12311211
> >
> > == Apache Camel 4.0.2 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1627/
> >
> > Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1627/org/apache/camel/camel/4.0.2/
> >
> > Tag: https://github.com/apache/camel/releases/tag/camel-4.0.2
> >
> > == Apache Camel Spring Boot 4.0.2 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1628/
> >
> > Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1628/org/apache/camel/springboot/spring-boot/4.0.2/
> >
> > Tag:
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.0.2
> >
> > Please test this release candidate and cast your vote:
> > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.0.2
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
>

Re: [VOTE] Release Apache Camel Kamelets 0.9.2

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Wed, Oct 26, 2022 at 10:40 AM Claus Ibsen  wrote:

> +1 (binding)
>
> On Wed, Oct 26, 2022 at 10:24 AM Andrea Cosentino 
> wrote:
>
> > Hello all:
> >
> > This is a vote for releasing only camel-kamelets 0.9.2.
> >
> > The release contains fixes.
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/0.9.2/
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1488
> > Kamelets Tag:
> >
> >
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v0.9.2
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 0.9.2
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 48 hours.
> >
> > NOTE: The vote for 48 hours is because there are no breaking changes but
> > the release is not really urgent.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: [VOTE] Release Apache Camel K 1.10.0 and related libraries

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Wed, Aug 31, 2022 at 1:55 PM Andrea Cosentino  wrote:

> Hello all:
>
> This is a combined vote to release Apache Camel K 1.10.0, Camel K Runtime
> 1.14.0 and Kamelets 0.9.0.
>
> This is a patch release based on Camel-Quarkus 2.11.3 and Camel 3.18.0 and
> contains several bug fixes and improvements.
>
> Runtime source files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/1.14.0/
> Runtime staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1465
> Runtime Tag:
>
> https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-project-1.14.0
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/0.9.0/
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1461
> Kamelets Tag:
>
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v0.9.0
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/1.10.0/
> Camel K Tag:
>
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.10.0
>
> Staging container image repository:
> https://hub.docker.com/r/camelk/camel-k/tags
>
> It's possible to install all staging artifacts with a single command:
>
> kamel install --operator-image=camelk/camel-k:1.10.0 --maven-repository=
> https://repository.apache.org/content/repositories/orgapachecamel-1465
>  --maven-repository=
> https://repository.apache.org/content/repositories/orgapachecamel-1461
>  --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel K 1.10.0, Apache Camel K Runtime
> 1.14.0 and Apache Camel Kamelets 0.9.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino
>

Re: [VOTE] Release Apache Camel Quarkus 2.12.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Aug 29, 2022 at 7:59 AM Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> Regards
> JB
>
> On Fri, Aug 26, 2022 at 7:07 PM Peter Palaga  wrote:
> >
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 2.12.0.
> >
> > Highlights:
> >
> > * Camel 3.18.1
> > * Quarkus 2.12.0.Final
> > * Fixed issues:
> >https://github.com/apache/camel-quarkus/milestone/31?closed=1
> > * All commits:
> >https://github.com/apache/camel-quarkus/compare/2.12.0...2.11.0
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1463
> >
> > Tag: https://github.com/apache/camel-quarkus/releases/tag/2.12.0
> >
> > Source release package:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1463/org/apache/camel/quarkus/camel-quarkus/2.12.0/camel-quarkus-2.12.0-src.zip
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binaries as Apache Camel Quarkus 2.12.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Many thanks to all contributors!
> >
> > -- Peter
> >
>

Re: [VOTE] Preview Release of Apache Camel Karavan 3.18.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Fri, Aug 12, 2022 at 7:38 AM Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> Regards
> JB
>
> On Fri, Aug 12, 2022 at 1:24 AM Marat Gubaidullin
>  wrote:
> >
> > Hello Camel Developers
> >
> > This is a vote for Preview release of Apache Camel Karavan 3.18.0
> >
> > Disclaimer:
> > Apache Camel Karavan version is aligned with Apache Camel version.
> > Karavan 3.18.0 is NOT LTS and still an experimental preview release.
> > Versions alignment is required to avoid DSL compatibility matrix between
> > Camel and Karavan.
> >
> > VS Code Extension (notes and extension)
> >
> https://github.com/apache/camel-karavan/releases/tag/untagged-316de529ee3c9be24ef7
> > <https://github.com/apache/camel-karavan/releases/tag/0.0.15>
> >
> > Karavan App for iPaaS
> >
> https://github.com/apache/camel-karavan/pkgs/container/camel-karavan/34663022?tag=3.18.0
> >
> > Karavan Builder Image for iPaaS
> >
> https://github.com/apache/camel-karavan/pkgs/container/camel-karavan-builder/34663875?tag=3.18.0
> >
> > Please test this release candidate and cast your vote.
> > [ ] +1 Release
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours starting from Monday, August 15,
> > 2022.
> >
> > Thanks,
> > Marat
>

Re: [VOTE] Release Apache Camel 3.18.1 LTS

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Aug 8, 2022 at 8:40 AM Gregor Zurowski 
wrote:

> Hi Everyone:
>
> This is a vote to release Apache Camel 3.18.1, a new patch release
> with 41 improvements and fixes.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352043=12311211
>
> == Apache Camel 3.18.1 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1450/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1450/org/apache/camel/apache-camel/3.18.1/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.18.1
>
> == Apache Camel Spring Boot 3.18.1 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1451/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.18.1
>
> == Apache Camel Karaf 3.18.1 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1452/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.18.1
>
> Please test this release candidate and cast your vote:
> [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> Karaf 3.18.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>

Re: [VOTE] Release Apache Camel K 1.9.0 and related libraries

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Fri, Apr 22, 2022 at 8:53 AM Antonin Stefanutti
 wrote:

> +1 (binding)
>
> Thanks Andrea!
>
> > On 21 Apr 2022, at 13:23, Andrea Cosentino  wrote:
> >
> > Hello all:
> >
> > This is a combined vote to release Apache Camel K 1.9.0, Camel K Runtime
> > 1.13.0 and Kamelets 0.8.0.
> >
> > This is a patch release based on Camel-Quarkus 2.8.0 and Camel 3.16.0 and
> > contains several bug fixes and improvements.
> >
> > Runtime source files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/1.13.0/
> > Runtime staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1427
> > Runtime Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-project-1.13.0
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/0.8.0/
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1426
> > Kamelets Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v0.8.0
> >
> > Camel K release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k/1.9.0/
> > Camel K Tag:
> > https://gitbox.apache.org/repos/asf?p=camel-k
> > .git;a=shortlog;h=refs/tags/v1.8.1
> >
> > Staging container image repository:
> https://hub.docker.com/r/camelk/camel-k
> > /tags
> >
> > It's possible to install all staging artifacts with a single command:
> >
> > kamel install --operator-image=camelk/camel-k:1.9.0 --maven-repository=
> > https://repository.apache.org/content/repositories/orgapachecamel-1426
> > --maven-repository=
> > https://repository.apache.org/content/repositories/orgapachecamel-1427
> > --olm=false
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel K 1.9.0, Apache Camel K Runtime
> > 1.13.0 and Apache Camel Kamelets 0.8.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
>
>

Re: [VOTE] Release Apache Camel Quarkus 2.8.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Apr 4, 2022 at 12:10 PM Babak Vahdat
 wrote:

> +1 (binding)
>
> Thanks James!
>
> Babak
>
> > On 4 Apr 2022, at 11:55, James Netherton 
> wrote:
> >
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 2.8.0.
> >
> > Highlights:
> >
> > * Camel 3.16.0
> > * Quarkus 2.8.0.Final
> >
> > All commits:
> >
> > https://github.com/apache/camel-quarkus/compare/2.8.0-M1...2.8.0
> >
> > Staging repository:
> >
> > https://repository.apache.org/content/repositories/orgapachecamel-1424
> >
> > Tag:
> >
> > https://github.com/apache/camel-quarkus/releases/tag/2.8.0
> >
> > Source release package:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1424/org/apache/camel/quarkus/camel-quarkus/2.8.0/camel-quarkus-2.8.0-src.zip
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binaries as Apache Camel Quarkus 2.8.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
>
>

Re: [VOTE] Release Apache Camel 3.16.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Thu, Mar 24, 2022 at 4:03 AM Babak Vahdat
 wrote:

> +1 (binding)
>
> Tested with own projects. Thanks Gregor!
>
> Babak
>
>
> On Wed, Mar 23, 2022 at 6:34 PM Gregor Zurowski  <mailto:gre...@list.zurowski.org>>
> wrote:
>
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 3.16.0, a new minor release
> > with 206 fixes and improvements.
> >
> > Release notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351219=12311211
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351219=12311211
> >
> >
> > == Apache Camel 3.16.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1420/
> <https://repository.apache.org/content/repositories/orgapachecamel-1420/>
> >
> > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1420/org/apache/camel/apache-camel/3.16.0/
> <
> https://repository.apache.org/content/repositories/orgapachecamel-1420/org/apache/camel/apache-camel/3.16.0/
> >
> >
> > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.16.0
> <
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.16.0
> >
> >
> > == Apache Camel Spring Boot 3.16.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1421/
> <https://repository.apache.org/content/repositories/orgapachecamel-1421/>
> >
> > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.16.0
> <
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.16.0
> >
> >
> > == Apache Camel Karaf 3.16.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1422/
> <https://repository.apache.org/content/repositories/orgapachecamel-1422/>
> >
> > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.16.0
> <
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.16.0
> >
> >
> > Please test this release candidate and cast your vote:
> > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > Karaf 3.16.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
>

Re: [VOTE] Release Apache Camel K 1.8.2

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Thu, Mar 3, 2022 at 2:27 PM Andrea Cosentino  wrote:

> Hello all,
>
> This is a vote to release Apache Camel K 1.8.2.
>
> This is a patch release containing an important fix:
> https://github.com/apache/camel-k/pull/3056
>
> This is a critical issue for basic camel-k usage. That's the main reason of
> this release.
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/1.8.2/
> Camel K Tag:
>
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.8.2
>
> Staging container image repository:
> https://hub.docker.com/r/camelk/camel-k/tags
>
> It's possible to install all staging artifacts with a single command:
> kamel install --operator-image=camelk/camel-k:1.8.2 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel K 1.8.2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 48 hours.
>
> The release vote window of 48 hours is related to the critical issue.
> There's nothing new added in this release, except fixes related to that
> issue.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino
>

Re: [VOTE] Release Apache Camel K 1.8.1 and related libraries

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Feb 21, 2022 at 11:43 AM Zoran Regvart  wrote:

> +1 (binding)
>
> Thanks Andrea!
>
> zoran
>
> On Mon, Feb 21, 2022 at 10:45 AM Andrea Cosentino 
> wrote:
> >
> > Hello all:
> >
> > This is a combined vote to release Apache Camel K 1.8.1, Camel K Runtime
> > 1.12.0 and Kamelets 0.7.1.
> >
> > This is a patch release based on Camel-Quarkus 2.7.0 and Camel 3.14.1 and
> > contains several bug fixes.
> >
> > Runtime source files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/1.12.0/
> > Runtime staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1411
> > Runtime Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-project-1.12.0
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/0.7.1/
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1410
> > Kamelets Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v0.7.1
> >
> > Camel K release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k/1.8.1/
> > Camel K Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.8.1
> >
> > Staging container image repository:
> > https://hub.docker.com/r/camelk/camel-k/tags
> >
> > It's possible to install all staging artifacts with a single command:
> >
> > kamel install --operator-image=camelk/camel-k:1.8.1 --maven-repository=
> > https://repository.apache.org/content/repositories/orgapachecamel-1410
> > --maven-repository=
> > https://repository.apache.org/content/repositories/orgapachecamel-1411
> > --olm=false
> >
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel K 1.8.1, Apache Camel K Runtime
> > 1.12.0 and Apache Camel Kamelets 0.7.1
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
>
>
>
> --
> Zoran Regvart
>

Re: [VOTE] Release Apache Camel 3.15.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Tue, Feb 1, 2022 at 2:43 PM Jean-Baptiste Onofré  wrote:

> +1 (binding)
>
> Regards
> JB
>
> On 01/02/2022 07:39, Gregor Zurowski wrote:
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 3.15.0, a new release with 217
> > new features and improvements.
> >
> > Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350874=12311211
> >
> > == Apache Camel 3.15.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1407/
> >
> > Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1407/org/apache/camel/apache-camel/3.15.0/
> >
> > Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.15.0
> >
> > == Apache Camel Spring Boot 3.15.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1408/
> >
> > Tag:
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.15.0
> >
> > == Apache Camel Karaf 3.15.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1409/
> >
> > Tag:
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.15.0
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > Karaf 3.15.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
>

Re: [VOTE] Release Apache Camel Quarkus 2.7.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Fri, Jan 28, 2022 at 5:10 PM Zheng Feng  wrote:

> +1
>
> Thanks James
>
> On Fri, Jan 28, 2022 at 5:46 PM James Netherton 
> wrote:
>
> > Hi everyone,
> >
> > This is a vote to release Apache Camel Quarkus 2.7.0.
> >
> > Highlights:
> >
> > * Camel 3.14.1
> > * Quarkus 2.7.0.Final
> > * Fixed issues:
> > https://github.com/apache/camel-quarkus/milestone/23?closed=1
> > * All commits:
> > https://github.com/apache/camel-quarkus/compare/2.6.0...2.7.0
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1405
> >
> > Tag:
> > https://github.com/apache/camel-quarkus/releases/tag/2.7.0
> >
> > Source release package:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1405/org/apache/camel/quarkus/camel-quarkus/2.7.0/camel-quarkus-2.7.0-src.zip
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel Quarkus 2.7.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> >
> > James
> >
>

Re: [VOTE] Release Apache Camel K 1.8.0 and related libraries

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Thu, Jan 20, 2022 at 7:21 AM Claus Ibsen  wrote:

> +1 (binding)
>
> On Wed, Jan 19, 2022 at 6:17 PM Andrea Cosentino 
> wrote:
> >
> > Hello all:
> >
> > This is a combined vote to release Apache Camel K 1.8.0, Camel K Runtime
> > 1.11.0 and Kamelets 0.7.0.
> >
> > This is a major release based on Camel-Quarkus 2.6.0 and Camel 3.14.0 and
> > contains several changes in both the operator and the runtime.
> >
> > Runtime source files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/1.11.0/
> > Runtime staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1401
> > Runtime Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-project-1.11.0
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/0.7.0/
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1400
> > Kamelets Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v0.7.0
> >
> > Camel K release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k/1.8.0/
> > Camel K Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.8.0
> >
> > Staging container image repository:
> https://hub.docker.com/r/camelk/camel-k
> > /tags
> >
> > It's possible to install all staging artifacts with a single command:
> > kamel install --operator-image=camelk/camel-k:1.8.0 --maven-repository=
> > https://repository.apache.org/content/repositories/orgapachecamel-1400
> > --maven-repository=
> > <https://repository.apache.org/content/repositories/orgapachecamel-1400>
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1401--olm=false
> > <https://repository.apache.org/content/repositories/orgapachecamel-1401>
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel K 1.8.0, Apache Camel K Runtime
> > 1.11.0 and Apache Camel Kamelets 0.7.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Andrea Cosentino
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: [HEADS UP] - Renaming inconsistent data format names in model

[Luca Burgazzoli]

On Tue, Jan 18, 2022 at 2:31 PM Claus Ibsen  wrote:

> On Tue, Jan 18, 2022 at 12:39 AM Marat Gubaidullin
>  wrote:
> >
> > 1. I could omit kebab cased properties in generator while we have both.
> > 2. When read YAML Karavan "camelize" properties and DSL. Internal Karavan
> > Camel Definitions are in camel case. So output YAML is also camel case.
> >
>
> Yeah we can do that and for Camel 3.15 have both camelCase and
> kebab-case in the yaml-dsl.
> Where kebab-case is deprecated.
>

I'm not very sure we can support both kebab anc camel case in
camel-yaml-dsl.json, (as
example,. there may be an issue with required properties) however we may
think to just
deprecate the kebab case in the json schema but we can keep support in the
yaml loader.


> This gives us that "wriggle room" to let kamelets, camel-k and others
> migrate to camelCase.
> Then in Camel 3.16 og 3.17 we can drop kebab and when we are fully
> migrated.
>
>
>
> > On Mon., Jan. 17, 2022, 09:49 Claus Ibsen  wrote:
> >
> > > On Mon, Jan 17, 2022 at 3:17 PM Marat Gubaidullin
> > >  wrote:
> > > >
> > > > Hello Claus,
> > > >
> > > > 1. There is a typo (gzipDeflator instead of gzipDeflater) in the data
> > > > format name
> > > >
> > >
> https://github.com/apache/camel/blob/4829e4b7c9fec2ea785411a1ccad65339e080520/core/camel-core-model/src/main/java/org/apache/camel/model/dataformat/DataFormatsDefinition.java#L57
> > > >
> > > > 2. I have fetched, built and still have data format names (and
> almost all
> > > > other properties) in kabab case in camel-yaml-dsl.json
> > > >
> > >
> > > One problem with having both camelCase and kebab-case in the
> > > camel-yaml-dsl.json is that you would have double properties for
> > > everything.
> > > Then in the tooling you would need to filter out the duplicated kebab
> > > based properties.
> > >
> > > Or we switch over to camelCase only. For the existing kamelets then we
> > > need to update those, but they are almost all in camelCase anyway.
> > > There is a few EIPs like set-header and set-property they are using,
> > > which should be setHeader and setProperty.
> > > So the migration is easy.
> > >
> > >
> > > >
> > > > On Mon, Jan 17, 2022 at 2:51 AM Claus Ibsen 
> > > wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > Just a heads up that I have squashed and merged this to the main
> > > branch.
> > > > >
> > > > > On Sun, Jan 16, 2022 at 3:12 PM Claus Ibsen  >
> > > wrote:
> > > > > >
> > > > > > Hi
> > > > > >
> > > > > > Ticket: https://issues.apache.org/jira/browse/CAMEL-17499
> > > > > >
> > > > > > The data formats have over the time become inconsistent in the
> model
> > > > > > and their names and also name vs camel-xxx JAR name etc.
> > > > > >
> > > > > > So after the 3.14 LTS release and where we drop JDK8 then we are
> > > doing
> > > > > > some house cleaning.
> > > > > > We also have some components to be marked as deprecated and to be
> > > > > removed later.
> > > > > >
> > > > > > The data format renaming is a more complex "thing" as we have a
> bunch
> > > > > > of source code generated files based on those names.
> > > > > >
> > > > > > So a rename of eg zipfile to zipFile (to use camel case) that
> causes
> > > > > > the generated files to keep the existing file name because the
> lower
> > > > > > case name existed. So to "fix" this a commit is needed to delete
> the
> > > > > > first, and then another to regenerate the files.
> > > > > >
> > > > > > So for all of this work I did this today on a quiet day but
> there is
> > > > > > about 50 commits in total as there are many regens in this line
> of
> > > > > > spirit to make it all work.
> > > > > >
> > > > > > I am not sure if a git quash would work?
> > > > > >
> > > > > > I pushed the code to a branch
> > > > > > https://github.com/apache/camel/tree/dataformat-rename
> > > > > >
> > > > > > And a bit PR (we can try to squash this one)
> > > > > > https://github.com/apache/camel/pull/6760
> > > > > >
> > > > > >
> > > > > > --
> > > > > > 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
> > >
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: [VOTE] Release Camel-Kamelets 0.6.0 (2nd attempt)

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Wed, Dec 22, 2021 at 2:21 PM Andrea Cosentino  wrote:

> Hello all:
>
> This is a vote for releasing only camel-kamelets 0.6.0 (the second
> attempt).
>
> The release contains new kamelets and fixes.
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/0.6.0/
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1393
> Kamelets Tag:
>
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v0.6.0
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 0.6.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino
>

Re: Deprecating and removing old and unmaintained components

[Luca Burgazzoli]

+1 to remove obsolete components

---
Luca Burgazzoli


On Mon, Dec 20, 2021 at 10:50 AM Claus Ibsen  wrote:

> Hi
>
> After the 3.14 LTS release, then it's a good time to look at cleaning
> up among the components we have that have become obsolete, because the
> 3rd party projects (dependencies) are EOL or not actively maintained
> for a longer period.
>
> The next LTS in summer 2022 is dropping Java 8, and as such it's a
> step forward so we should use this opportunity to do some
> house-cleaning.
>
> camel-beanstalk
> camel-etc
> camel-elsql
> camel-ganglia
> camel-nsq
> camel-hystrix
> camel-ipfs (JARs not in maven central)
> camel-jing
> camel-leveldb-legacy
> camel-msv
> camel-nagios
> camel-ribbon
> camel-sip
> camel-soroush
> camel-tagsoup
> camel-yammer
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: [VOTE] Release Camel-Kamelets 0.6.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Dec 20, 2021 at 7:21 AM Andrea Cosentino  wrote:

> Hello all:
>
> This is a vote for releasing only camel-kamelets 0.6.0
>
> The release contains new kamelets and fixes.
>
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1392
> Kamelets Tag:
>
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v0.6.0
>
> Please cast your vote.
>
> [ ] +1 Release camel-kamelets 0.6.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Andrea Cosentino
>

Re: [VOTE] Release Apache Camel Quarkus 2.6.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Sat, Dec 18, 2021 at 3:08 PM Zoran Regvart  wrote:

> +1 (binding)
>
> Thanks Zineb!
>
> zoran
>
> On Sat, Dec 18, 2021 at 2:38 PM Zineb Bendhiba 
> wrote:
> >
> > Hello all,
> >
> > This is a vote to release Apache Camel Quarkus 2.6.0.
> >
> > Highlights:
> >
> > * Camel 3.14.0
> > * Quarkus 2.6.0.Final
> > * Fixed issues:
> > https://github.com/apache/camel-quarkus/milestone/22?closed=1
> > * All commits:
> > https://github.com/apache/camel-quarkus/compare/2.5.0...2.6.0
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1391/
> >
> > Tag:
> > https://github.com/apache/camel-quarkus/releases/tag/2.6.0
> >
> > Source release package:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1391/org/apache/camel/quarkus/camel-quarkus/2.6.0/camel-quarkus-2.6.0-src.zip
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel Quarkus 2.6.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> >
> >
> > --
> > Zineb
>
>
>
> --
> Zoran Regvart
>

Re: [VOTE] Release Apache Camel Quarkus 2.5.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Nov 22, 2021 at 1:13 PM Peter Palaga  wrote:

> +1 (binding)
>
> Thanks for performing the release, Zineb!
>
> -- Peter
>
> On 19/11/2021 14:22, Zineb Bendhiba wrote:
> > Hello all,
> >
> > This is a vote to release Apache Camel Quarkus 2.5.0.
> >
> > Highlights:
> >
> > * Camel 3.13.0
> > * Quarkus 2.5.0.Final
> > * Fixed issues:
> > https://github.com/apache/camel-quarkus/milestone/21?closed=1
> > * All commits:
> > https://github.com/apache/camel-quarkus/compare/2.4.0...2.5.0
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1379/
> >
> > Tag:
> > https://github.com/apache/camel-quarkus/releases/tag/2.5.0
> >
> > Source release package:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1379/org/apache/camel/quarkus/camel-quarkus/2.5.0/camel-quarkus-2.5.0-src.zip
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel Quarkus 2.5.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> >
>
>

Re: [VOTE] Release Apache Camel 3.13.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Tue, Nov 9, 2021 at 7:32 PM Alexandre Gallice 
wrote:

> +1 (binding)
>
> Well done :)
> Alex
>
> On Tue, Nov 9, 2021 at 6:50 PM Jean-Baptiste Onofre 
> wrote:
>
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > > Le 9 nov. 2021 à 08:08, Gregor Zurowski  a
> > écrit :
> > >
> > > Hi Everyone:
> > >
> > > This is a vote to release Apache Camel 3.13.0, a new release with 119
> > > new features and improvements.
> > >
> > > Release notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350624=12311211
> > >
> > > == Apache Camel 3.13.0 ==
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1371/
> > >
> > > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1371/org/apache/camel/apache-camel/3.13.0/
> > >
> > > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.13.0
> > >
> > > == Apache Camel Spring Boot 3.13.0 ==
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1372/
> > >
> > > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.13.0
> > >
> > > == Apache Camel Karaf 3.13.0 ==
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1373/
> > >
> > > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.13.0
> > >
> > > Please test this release candidate and cast your vote.
> > > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > > Karaf 3.13.0
> > > [ ] -1 Veto the release (provide specific comments)
> > >
> > > The vote is open for at least 72 hours.
> > >
> > > Thanks,
> > > Gregor
> >
> >
>

Re: [VOTE] Release Apache Camel K 1.7.0 and related libraries

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Wed, Nov 10, 2021 at 1:28 PM Nicola Ferraro  wrote:

> Hello all:
>
> This is a combined vote to release Apache Camel K 1.7.0, Camel K Runtime
> 1.10.0 and Kamelets 0.5.0.
>
> This is a major release based on Camel-Quarkus 2.4.0 and Camel 3.12.0 and
> contains several changes in both the operator and the runtime. More details
> in the release notes:
> https://github.com/apache/camel-k/issues/2743#issue-1049758847
>
> Runtime source files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/1.10.0/
> Runtime staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1374
> Runtime Tag:
>
> https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-project-1.10.0
>
> Kamelets release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/0.5.0/
> Kamelets staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1375
> Kamelets Tag:
>
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v0.5.0
>
> Camel K release files:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/1.7.0/
> Camel K Tag:
>
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.7.0
>
> Staging container image repository:
> https://hub.docker.com/r/camelk/camel-k
> /tags
>
> It's possible to install all staging artifacts with a single command:
> kamel install --operator-image=camelk/camel-k:1.7.0 --maven-repository=
> https://repository.apache.org/content/repositories/orgapachecamel-1374
> --maven-repository=
> <https://repository.apache.org/content/repositories/orgapachecamel-1374--maven-repository=>
> https://repository.apache.org/content/repositories/orgapachecamel-1375
> --olm=false
> <https://repository.apache.org/content/repositories/orgapachecamel-1375--olm=false>
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel K 1.7.0, Apache Camel K Runtime
> 1.10.0 and Apache Camel Kamelets 0.5.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Here's my +1.
>
> Thanks,
> Nicola Ferraro
>

Re: [VOTE] Release Apache Camel K 1.6.1 and related libraries

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Oct 25, 2021 at 2:15 PM Otavio Rodolfo Piske 
wrote:

> +1 (non-binding)
>
> Thanks Nicola!
>
> On Mon, Oct 25, 2021 at 11:24 AM Antonin Stefanutti
>  wrote:
>
> > +1 (non-binding)
> >
> > Thanks Nicola!
> >
> > > On 23 Oct 2021, at 20:27, Nicola Ferraro  wrote:
> > >
> > > Hello all:
> > >
> > > This is a combined vote to release Apache Camel K 1.6.1 and Camel K
> > Runtime
> > > 1.9.1.
> > >
> > > This is a minor release upgrading the runtime to Camel-Quarkus
> > > 2.3.0 and Camel 3.11.2 and contains some fixes in the operator. More
> > > details in the release notes:
> > > https://github.com/apache/camel-k/issues/2713#issue-1034225593
> > >
> > > Runtime source files:
> > > https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/1.9.1/
> > > Runtime staging repository:
> > > https://repository.apache.org/content/repositories/orgapachecamel-1369
> > >
> > > Runtime Tag:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-project-1.9.1
> > >
> > > Camel K release files:
> > > https://dist.apache.org/repos/dist/dev/camel/camel-k/1.6.1/
> > > Camel K Tag:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.6.1
> > >
> > > Staging container image repository:
> > > https://hub.docker.com/r/camelk/camel-k/tags
> > >
> > > It's possible to install all staging artifacts with a single command:
> > > kamel install --operator-image camelk/camel-k:1.6.1 --maven-repository
> > > https://repository.apache.org/content/repositories/orgapachecamel-1369
> > > --olm=false
> > >
> > > Please test this release candidate and cast your vote.
> > >
> > > [ ] +1 Release the binary as Apache Camel K 1.6.1 and
> > > Apache Camel K Runtime 1.9.1
> > > [ ] -1 Veto the release (provide specific comments)
> > >
> > > The vote is open for at least 72 hours.
> > >
> > > Here's my +1.
> > >
> > > Thanks,
> > > Nicola Ferraro
> >
> >
>
> --
> Otavio R. Piske
> http://orpiske.net
>

Re: [VOTE] Release Apache Camel Quarkus 2.4.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Sat, Oct 23, 2021 at 5:33 PM Zheng Feng  wrote:

> +1 (non-binding)
>
> Thanks Peter !
>
>
>
> On Sat, Oct 23, 2021 at 12:10 AM Peter Palaga  wrote:
>
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 2.4.0.
> >
> > Highlights:
> >
> > * Camel 3.12.0
> > * Quarkus 2.4.0.Final
> > * Fixed issues:
> >https://github.com/apache/camel-quarkus/milestone/20?closed=1
> > * All commits:
> >https://github.com/apache/camel-quarkus/compare/2.4.0...2.3.0
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1370
> >
> > Tag: https://github.com/apache/camel-quarkus/releases/tag/2.4.0
> >
> > Source release package:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1370/org/apache/camel/quarkus/camel-quarkus/2.4.0/camel-quarkus-2.4.0-src.zip
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binaries as Apache Camel Quarkus 2.4.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Many thanks to all contributors!
> >
> > -- Peter
> >
> >
>

Re: [VOTE] Release Apache Camel 3.12.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Wed, Sep 29, 2021 at 2:58 PM Andrea Cosentino  wrote:

> +1 (binding)
>
> Thanks Gregor.
>
> Il giorno mer 29 set 2021 alle ore 09:58 Gregor Zurowski <
> gre...@list.zurowski.org> ha scritto:
>
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 3.12.0, a new release with 206
> > new features and improvements.
> >
> > Release notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350283=12311211
> >
> > == Apache Camel 3.12.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1359/
> >
> > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1359/org/apache/camel/apache-camel/3.12.0/
> >
> > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.12.0
> >
> > == Apache Camel Spring Boot 3.12.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1360/
> >
> > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.12.0
> >
> > == Apache Camel Karaf 3.12.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1361/
> >
> > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.12.0
> >
> > Please test this release candidate and cast your vote.
> > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > Karaf 3.12.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
> >
>

Re: Karavan project: Integration Designer for Camel/Camel-K

[Luca Burgazzoli]

Hi Marat,

I do agree with Andrea and Claus: it is an awesome project and it would be
very nice addition to the camel ecosystem.
The only thing that would make it even more awesome (not sure if technical
possible) would be having a support for VS Code and http://github.dev.

---
Luca Burgazzoli


On Fri, Sep 24, 2021 at 9:50 AM Claus Ibsen  wrote:

> Hi Marat
>
> Yay this looks great. I like that the editor is dis-connected from
> Camel, where you can either save the generated file to disk,
> or push to a git repository.
>
> It also seems you use the EIP json files from the catalog to list the EIPs.
> I noticed we didn't have them labelled too nicely so I will polish
> this in the camel-core.
>
>
> On Thu, Sep 23, 2021 at 1:55 AM Marat Gubaidullin
>  wrote:
> >
> > Hello Camel Developers,
> >
> > For the last few months I've been working on the Karavan project:
> > Integration Designer for Camel/Camel-K.
> > https://github.com/mgubaidullin/karavan
> >
> > Karavan is still in the preliminary/experimental stage, however it is
> > possible to "draw" an integration. It already supports Kamelets and a lot
> > of EIP. It works in local mode to store YAMLs on a local machine. In
> cloud
> > mode <
> https://github.com/mgubaidullin/karavan/blob/main/openshift/README.md>
> > Karavan stores YAMLs into a git repository for deployment using GitOps
> > techniques.
> >
> > Karavan demos:
> > 1. Basic integration design: https://youtu.be/a2xPcSE4TxA
> > 2. Cloud mode demo: https://youtu.be/CUCpw1UFLCc
> >
> > I would like to donate the Karavan project to ASF to run it as a Camel
> sub
> > project and continue to work on it together with the Camel Community.
> >
> > What do you think?
> >
> > Thanks
> > Marat Gubaidullin
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: [HEADS-UP][DISCUSS] migrating Camel Kafka Connector to use kamelets

[Luca Burgazzoli]

On Mon, Sep 20, 2021 at 9:12 AM Claus Ibsen  wrote:

>
> If a old connector is needed we could ship the maven plugin so CKC
> users can generate a custom connector themseleves as "fallback"
>
>
Wonder if the generation of a camel kafka connector could also be a target
for https://github.com/apache/camel-kameleon

Re: [discuss] find a better name for KameletBinding

[Luca Burgazzoli]

Opened an issue on camel-k to rename KameletBinding to Binding:
https://github.com/apache/camel-k/issues/2625

---
Luca Burgazzoli


On Fri, Aug 27, 2021 at 10:14 PM Marat Gubaidullin <
marat.gubaidul...@gmail.com> wrote:

> Hi!
> It looks like we already have "Bindings" but it was deprecated
>
>
> https://docs.openshift.com/container-platform/3.7/rest_api/api/v1.Binding.html
>
> On Fri, Aug 20, 2021 at 6:18 AM Claus Ibsen  wrote:
>
> > Hi
> >
> > Yeah one of the hardest problem is naming, and after that renaming as
> > a lot of old stuff "expects" the old name.
> >
> > I am also leading to Binding, as we have other concepts in Camel K
> > that are neutral named (no Camel or product in the name) like
> > Integration, IntegrationKit.
> > And they are all in the same namespace, so there are no clash on
> > kubernetes.
> >
> > +1 for Binding
> >
> >
> >
> > On Fri, Aug 20, 2021 at 10:59 AM John Poth  wrote:
> > >
> > > +1 for Binding
> > >
> > > Dropping the Kamelet part makes it clearer that you can bind more
> > > than just Kamelets.
> > >
> > > Keeping it as "Binding" gives Kubernetes users a pretty good idea of
> what
> > > it's going to do without reading the documentation.
> > >
> > > On Mon, Aug 16, 2021 at 2:04 PM Antonin Stefanutti
> > >  wrote:
> > >
> > > > Hi Luca, all,
> > > >
> > > > +1 for Binding.
> > > >
> > > > Users in the Kubernetes ecosystem may already be familiar with the
> > term,
> > > > as it seems it's the choice made by projects like Knative and Service
> > > > Binding,
> > > > to convey the general concept of "integrating" in their respective
> > domain.
> > > >
> > > > I find projecting that concept into the integration domain to be a
> good
> > > > fit, which
> > > > Would materialises in Kubernetes as bindings.camel.apache.org<
> > > > http://bindings.camel.apache.org> resources.
> > > >
> > > > On 16 Aug 2021, at 10:27, Luca Burgazzoli  >  > > > lburgazz...@gmail.com>> wrote:
> > > >
> > > > Hello,
> > > >
> > > > When the KameletBinding concept was introduced in camel-k, if was
> > meant to
> > > > bind two Kamelets and nothing more, but over time we have added more
> > > > capabilities, like:
> > > >
> > > > - support for processing steps to transform exchanges/messages
> > > > - support to address/source from different systems so the source/sink
> > does
> > > > not need be a kamelet anymore
> > > >
> > > > So I think the term KameletBinding is not more appropriate and to
> > reduce
> > > > confusion, we should try to find a better name.
> > > >
> > > > On top of my mind, I'd see the following names as a possible
> > replacement:
> > > > - Binding so leave Kamelet out of the game as Kamelets are one of the
> > > > option but not the exclusive on
> > > > - Connector as in essence, a KameletBinding describe how to connect A
> > to B
> > > >
> > > > Any opinion ?
> > > >
> > > > ---
> > > > Luca Burgazzoli
> > > >
> > > >
> >
> >
> >
> > --
> > Claus Ibsen
> > -
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>

Re: [VOTE] Release Apache Camel K 1.5.1

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Sun, Aug 29, 2021 at 2:53 PM Claus Ibsen  wrote:

> +1 (binding)
>
> On Fri, Aug 27, 2021 at 5:34 PM Nicola Ferraro 
> wrote:
> >
> > Hello all:
> >
> > This is a vote to release Apache Camel K 1.5.1.
> >
> > This release fixes general bugs in the 1.5.x stream. More details on the
> > release notes:
> > https://github.com/apache/camel-k/issues/2590#issuecomment-907287186
> >
> > Camel K staging repository:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k/1.5.1/
> > Camel K Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.5.1
> >
> > Staging container image repository:
> > https://hub.docker.com/r/camelk/camel-k/tags
> >
> > It's possible to install all staging artifacts with a single command:
> > kamel install --operator-image=camelk/camel-k:1.5.1 --olm=false
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel K 1.5.1
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Nicola Ferraro
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: [VOTE] Release Apache Camel Quarkus 2.2.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Sun, Aug 29, 2021 at 10:32 PM James Netherton 
wrote:

> +1 (binding)
>
> Thanks Peter!
>
> On Fri, 27 Aug 2021 at 17:24, Peter Palaga  wrote:
>
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 2.2.0.
> >
> > Highlights:
> >
> > * Quarkus 2.2.0.Final
> > * Fixed issues:
> >https://github.com/apache/camel-quarkus/milestone/18?closed=1
> > * All commits:
> >https://github.com/apache/camel-quarkus/compare/2.2.0...2.1.0
> > * Migration guide:
> >
> > https://camel.apache.org/camel-quarkus/latest/migration-guide/2.2.0.html
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1350
> >
> > Tag: https://github.com/apache/camel-quarkus/releases/tag/2.2.0
> >
> > Source release package:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1350/org/apache/camel/quarkus/camel-quarkus/2.2.0/camel-quarkus-2.2.0-src.zip
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binaries as Apache Camel Quarkus 2.2.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Many thanks to all contributors!
> >
> > -- Peter
> >
> >
>

[discuss] find a better name for KameletBinding

[Luca Burgazzoli]

Hello,

When the KameletBinding concept was introduced in camel-k, if was meant to
bind two Kamelets and nothing more, but over time we have added more
capabilities, like:

- support for processing steps to transform exchanges/messages
- support to address/source from different systems so the source/sink does
not need be a kamelet anymore

So I think the term KameletBinding is not more appropriate and to reduce
confusion, we should try to find a better name.

On top of my mind, I'd see the following names as a possible replacement:
- Binding so leave Kamelet out of the game as Kamelets are one of the
option but not the exclusive on
- Connector as in essence, a KameletBinding describe how to connect A to B

Any opinion ?

---
Luca Burgazzoli

Re: [VOTE] Release Apache Camel K 1.5.0 and related libraries

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Tue, Jul 6, 2021 at 2:37 AM Zheng Feng  wrote:

> +1 (binding)
>
> On Mon, Jul 5, 2021 at 6:54 PM Nicola Ferraro  wrote:
>
> > Hello all:
> >
> > This is a combined vote to release Apache Camel K 1.5.0, Camel K Runtime
> > 1.8.0 and Kamelets 0.3.0 (the camel-kamelet repository is now released in
> > Maven).
> >
> > This is a major release based on Camel-Quarkus 2.0.0 and Camel 3.11.0 and
> > contains several changes in both the operator and the runtime. More
> details
> > in the release notes:
> > https://github.com/apache/camel-k/issues/2470#issuecomment-872856803
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/1.8.0/
> > Runtime staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1342
> > Runtime Tag:
> >
> >
> https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-project-1.8.0
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/0.3.0/
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1341
> > Kamelets Tag:
> >
> >
> https://gitbox.apache.org/repos/asf?p=camel-kamelets.git;a=shortlog;h=refs/tags/v0.3.0
> >
> > Camel K release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k/1.5.0/
> > Camel K Tag:
> >
> >
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.5.0
> >
> > Staging container image repository:
> > https://hub.docker.com/r/camelk/camel-k/tags
> >
> > It's possible to install all staging artifacts with a single command:
> > kamel install --operator-image=camelk/camel-k:1.5.0 --maven-repository=
> > https://repository.apache.org/content/repositories/orgapachecamel-1341
> > --maven-repository=
> > <
> https://repository.apache.org/content/repositories/orgapachecamel-1341--maven-repository=
> >
> > https://repository.apache.org/content/repositories/orgapachecamel-1342
> > --olm=false
> > <
> https://repository.apache.org/content/repositories/orgapachecamel-1342--olm=false
> >
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel K 1.5.0, Apache Camel K Runtime
> > 1.8.0 and Apache Camel Kamelets 0.3.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Here's my +1.
> >
> > Thanks,
> > Nicola Ferraro
> >
>

Re: [VOTE] Release Apache Camel 3.11.0 (LTS)

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Wed, Jun 23, 2021 at 8:46 PM Gregor Zurowski 
wrote:

> Hi Everyone:
>
> This is a vote to release Apache Camel 3.11.0, a new LTS release with
> 101 improvements and fixes.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350096=12311211
>
> == Apache Camel 3.11.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1336/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1336/org/apache/camel/apache-camel/3.11.0/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.11.0
>
> == Apache Camel Spring Boot 3.11.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1337/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.11.0
>
> == Apache Camel Karaf 3.11.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1338/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.11.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> Karaf 3.11.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>

Re: [VOTE] Release Apache Camel Quarkus 2.0.0-M2

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Thu, Jun 10, 2021 at 4:19 PM Peter Palaga  wrote:

> Hi,
>
> This is a vote to release Apache Camel Quarkus 2.0.0-M1.
>
> It is another milestone release based on Camel 3.10.0 and Quarkus
> 2.0.0.CR3 to allow testing and gather feedback.
>
> Highlights:
>
> * Fixed issues:
>https://github.com/apache/camel-quarkus/milestone/16?closed=1
> * All commits:
>https://github.com/apache/camel-quarkus/compare/2.0.0-M1...2.0.0-M2
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1325
>
> Tag: https://github.com/apache/camel-quarkus/releases/tag/2.0.0-M2
>
> Source release package:
>
> https://repository.apache.org/content/repositories/orgapachecamel-1325/org/apache/camel/quarkus/camel-quarkus/2.0.0-M2/camel-quarkus-2.0.0-M2-src.zip
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binaries as Apache Camel Quarkus 2.0.0-M2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 48 hours.
>
> Many thanks to all contributors!
>
> -- Peter
>
>

Re: [VOTE] Release Apache Camel Quarkus 2.0.0-M1

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Wed, May 26, 2021 at 5:31 PM Andrea Cosentino  wrote:

> +1 (binding)
>
> Thanks Peter
>
> Il mer 26 mag 2021, 17:14 Peter Palaga  ha scritto:
>
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 2.0.0-M1.
> >
> > It is a milestone release based on Camel 3.10.0 and Quarkus 2.0.0.Alpha3
> > to allow testing and gather feedback.
> >
> > Highlights:
> >
> > * Fixed issues:
> >https://github.com/apache/camel-quarkus/milestone/13?closed=1
> > * All commits:
> >https://github.com/apache/camel-quarkus/compare/1.8.1...2.0.0-M1
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1324
> >
> > Tag: https://github.com/apache/camel-quarkus/releases/tag/2.0.0-M1
> >
> > Source release package:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1324/org/apache/camel/quarkus/camel-quarkus/2.0.0-M1/camel-quarkus-2.0.0-M1-src.zip
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binaries as Apache Camel Quarkus 2.0.0-M1
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 48 hours.
> >
> > Many thanks to all contributors!
> >
> > -- Peter
> >
> >
>

Re: [VOTE] Release Apache Camel 3.10.0 with Spring Boot and Karaf Support Projects

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, May 17, 2021 at 12:07 PM Zoran Regvart  wrote:

> +1 (binding)
>
> Thanks Gregor!
>
> On Mon, May 17, 2021 at 9:16 AM Gregor Zurowski
>  wrote:
> >
> > Hi Everyone:
> >
> > Resending this email as I missed prefixing the subject of the previous
> > email with VOTE.
> >
> > This is a vote to release Apache Camel 3.10.0 (with Apache Camel
> > Spring Boot and Apache Camel Karaf), a new minor release with 208
> > improvements and fixes.
> >
> > Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350004=12311220
> >
> > == Apache Camel 3.10.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1316/
> >
> > Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1316/org/apache/camel/apache-camel/3.10.0/
> >
> > Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.10.0
> >
> > == Apache Camel Spring Boot 3.10.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1317/
> >
> > Tag:
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.10.0
> >
> > == Apache Camel Karaf 3.10.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1318/
> >
> > Tag:
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.10.0
> >
> > Please test this release candidate and cast your vote.
> > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > Karaf 3.10.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
>
>
>
> --
> Zoran Regvart
>

Re: [VOTE] Release Apache Camel K 1.4.0 and Runtime 1.7.0 (Attempt #2)

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Apr 19, 2021 at 11:28 AM Alexandre Gallice 
wrote:

> Good catch Nicola. I'm delighted to cast a positive vote :)
>
> +1 (binding)
>
> Alex
>
> On Mon, Apr 19, 2021 at 10:26 AM Omar Al-Safi  wrote:
>
> > +1 (binding)
> >
> > Regards,
> > Omar
> >
> > On Mon, Apr 19, 2021 at 10:24 AM Nicola Ferraro 
> > wrote:
> >
> > > Hi Alex, may it be a sync issue with mirrors? I see the new package
> (both
> > > dates and obj links are ok).
> > >
> > > [nferraro@localhost test-release]$ curl --silent
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/camel/camel-k/1.4.0/camel-k-client-1.4.0-linux-64bit.tar.gz
> > > -o
> > > <
> >
> https://dist.apache.org/repos/dist/dev/camel/camel-k/1.4.0/camel-k-client-1.4.0-linux-64bit.tar.gz-o
> > >
> > > camel-k-client-1.4.0-linux-64bit.tar.gz
> > > [nferraro@localhost test-release]$
> > > [nferraro@localhost test-release]$ tar -xzf
> > > camel-k-client-1.4.0-linux-64bit.tar.gz
> > > [nferraro@localhost test-release]$
> > > [nferraro@localhost test-release]$ ls -l
> > > total 102916
> > > -rw-rw-r--. 1 nferraro nferraro 30136299 Apr 19 10:19
> > > camel-k-client-1.4.0-linux-64bit.tar.gz
> > > -rwxrwxr-x. 1 nferraro nferraro 75219356 Apr 17 01:05 kamel
> > > -rw-rw-r--. 1 nferraro nferraro  833 Apr 17 01:05 kamel.asc
> > > -rw-rw-r--. 1 nferraro nferraro  136 Apr 17 01:05 kamel.sha512
> > > -rw-rw-r--. 1 nferraro nferraro11359 Apr 17 01:05 LICENSE
> > > -rw-rw-r--. 1 nferraro nferraro  595 Apr 17 01:05 NOTICE
> > > [nferraro@localhost test-release]$
> > > [nferraro@localhost test-release]$ objdump -T kamel
> > >
> > > kamel: file format elf64-x86-64
> > >
> > > objdump: kamel: not a dynamic object
> > > DYNAMIC SYMBOL TABLE:
> > > no symbols
> > >
> > > Nicola
> > >
> > > On Mon, Apr 19, 2021 at 9:46 AM Alexandre Gallice <
> aldettin...@gmail.com
> > >
> > > wrote:
> > >
> > > > Are we sure that apache dist has been updated according to attempt
> #2 ?
> > > > When I download the client, it's still dynamically linked and more
> over
> > > the
> > > > date from the archive seems to be april the 13th ?
> > > >
> > > > On Mon, Apr 19, 2021 at 9:39 AM Claus Ibsen 
> > > wrote:
> > > >
> > > > > +1 (binding)
> > > > >
> > > > > On Sat, Apr 17, 2021 at 1:23 AM Nicola Ferraro <
> nferr...@apache.org>
> > > > > wrote:
> > > > > >
> > > > > > Hello all:
> > > > > >
> > > > > > This is a vote to release Apache Camel K 1.4.0 and Camel K
> Runtime
> > > > 1.7.0
> > > > > > (attempt #2).
> > > > > >
> > > > > > This release is based on Camel-Quarkus 1.8.1 and Camel 3.9.0 and
> > > > contains
> > > > > > several changes in both the operator and the runtime. More
> details
> > in
> > > > the
> > > > > > release notes: https://github.com/apache/camel-k
> > > > > > /issues/2134#issuecomment-819081192
> > > > > >
> > > > > > Runtime staging repository:
> > > > > >
> > > https://repository.apache.org/content/repositories/orgapachecamel-1310
> > > > > > Runtime Tag: https://gitbox.apache.org/repos/asf?p=camel-k
> > > > > > -runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-project-1.7.0
> > > > > >
> > > > > > Camel K staging repository:
> > > > > https://dist.apache.org/repos/dist/dev/camel/
> > > > > > camel-k/1.4.0/
> > > > > > Camel K Tag: https://gitbox.apache.org/repos/asf?p=camel-k
> > > > > > .git;a=shortlog;h=refs/tags/v1.4.0
> > > > > >
> > > > > > Staging container image repository:
> > > > > https://hub.docker.com/r/camelk/camel-k
> > > > > > /tags
> > > > > >
> > > > > > It's possible to install all staging artifacts with a single
> > command:
> > > > > > kamel install --operator-image=camelk/camel-k:1.4.0
> > > --maven-repository=
> > > > > >
> > > https://repository.apache.org/content/repositories/orgapachecamel-1310
> > > > > > --olm=false
> > > > > >
> > > > > > Note: remember to re-download binary files and make sure your
> > cluster
> > > > > > re-fetches the container image if you've tried attempt #1
> > > > > >
> > > > > > Please test this release candidate and cast your vote.
> > > > > >
> > > > > > [ ] +1 Release the binary as Apache Camel K 1.4.0 and Apache
> Camel
> > K
> > > > > Runtime
> > > > > > 1.7.0
> > > > > > [ ] -1 Veto the release (provide specific comments)
> > > > > >
> > > > > > The vote is open for at least 72 hours.
> > > > > >
> > > > > > Here's my +1.
> > > > > >
> > > > > > Thanks,
> > > > > > Nicola Ferraro
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Claus Ibsen
> > > > > -
> > > > > http://davsclaus.com @davsclaus
> > > > > Camel in Action 2: https://www.manning.com/ibsen2
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] Release Apache Camel-kafka-connector 0.9.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Wed, Mar 31, 2021 at 11:04 AM Andrea  wrote:

> Hello all,
>
> This is a vote to release Apache Camel-kafka-connector 0.9.0
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1307
>
> Tag:
>
> https://gitbox.apache.org/repos/asf?p=camel-kafka-connector.git;a=tag;h=refs/tags/camel-kafka-connector-0.9.0
>
> Aligned to camel 3.9.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as  Apache Camel-kafka-connector 0.9.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 48 hours.
>
> Thanks,
> Andrea.
>

Re: [VOTE] Release Apache Camel Quarkus 1.8.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Mar 29, 2021 at 10:57 AM Zheng Feng  wrote:

> +1
>
> On Fri, Mar 26, 2021 at 11:58 PM Peter Palaga  wrote:
>
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 1.7.0.
> >
> > Highlights:
> >
> > * Camel 3.9.0
> > * Quarkus 1.13.0.Final
> > * Fixed issues:
> >https://github.com/apache/camel-quarkus/milestone/12?closed=1
> > * Known issues:
> >* https://github.com/apache/camel-quarkus/issues/2207
> > * All commits:
> >https://github.com/apache/camel-quarkus/compare/1.7.0...1.8.0
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1306
> >
> > Tag: https://github.com/apache/camel-quarkus/releases/tag/1.8.0
> >
> > Source release package:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1306/org/apache/camel/quarkus/camel-quarkus/1.8.0/camel-quarkus-1.8.0-src.zip
> >
> > As long as Camel 3.9.0 is not publicly available, you have to add its
> > staging repo
> > https://repository.apache.org/content/repositories/orgapachecamel-1302
> > to your settings.xml to be able to test Camel Quarkus 1.8.0.
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel Quarkus 1.8.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Many thanks to all contributors!
> >
> > -- Peter
> >
> >
>

Re: [VOTE] Release Apache Camel K 1.3.2

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Mar 22, 2021 at 11:37 AM Otavio Rodolfo Piske 
wrote:

> +1 (non-binding)
>
> On Sun, Mar 21, 2021 at 10:26 PM Andrea  wrote:
>
> > +1 (not binding)
> >
> > On Sat, Mar 20, 2021, at 07:44, Claus Ibsen wrote:
> > > +1 (binding)
> > >
> > > On Fri, Mar 19, 2021 at 7:04 PM Nicola Ferraro  > <mailto:nferraro%40apache.org>> wrote:
> > > >
> > > > Hello all:
> > > >
> > > > This is a vote to release Apache Camel K 1.3.2.
> > > >
> > > > This is a minor release fixing bugs and improving support for
> Kamelets.
> > > > More details on the release notes:
> > > > https://github.com/apache/camel-k/issues/2144#issuecomment-803013372
> > > >
> > > > Camel K staging repository:
> > > > https://dist.apache.org/repos/dist/dev/camel/camel-k/1.3.2/
> > > > Camel K Tag:
> > > >
> >
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.3.2
> > > >
> > > > Staging container image repository:
> > > > https://hub.docker.com/r/camelk/camel-k/tags
> > > >
> > > > It's possible to install all staging artifacts with a single command:
> > > > kamel install --operator-image=camelk/camel-k:1.3.2 --olm=false
> > > >
> > > > Please test this release candidate and cast your vote.
> > > >
> > > > [ ] +1 Release the binary as Apache Camel K 1.3.2
> > > > [ ] -1 Veto the release (provide specific comments)
> > > >
> > > > The vote is open for at least 72 hours.
> > > >
> > > > Thanks,
> > > > Nicola Ferraro
> > >
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -
> > > http://davsclaus.com @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >
> >
>
>
> --
> Otavio R. Piske
> http://orpiske.net
>

Re: [HEADSUP] YAML DSL in Camel

[Luca Burgazzoli]

I've opened an PR with some initial code [1] and it is failing for a
circular dependency as the DSL need the camel-catalog to support a sort of
EndpointDSL for YAML which allow to write something like:

- from:
direct:
name: "start"
steps:
  - telegram:
  type: bots
  token: {{auth-token}}

So I wonder if we should bring the DSL as part of the code modules so it
can run after camel-allcomponents.

[1] https://github.com/apache/camel/pull/5119

---
Luca Burgazzoli


On Wed, Feb 24, 2021 at 9:42 AM Luca Burgazzoli 
wrote:

> On Wed, Feb 24, 2021 at 9:33 AM Claus Ibsen  wrote:
>
>> Hi
>>
>> Dont you have a "problem" with the flow style that you can't "end" the
>> split and do something after it
>>
>> For example having a split in the middle, where a and b are outside
>> the splitter then you can do in Java as
>>
>> from x
>> to a
>> split
>> to sub 1
>> to sub 2
>> end
>> to b
>>
>
> Yes absolutely and that's why I have not re-implemented it.
> It also make the json schema validation a little weak as you cannot mark
> steps as required.
>
> Just for reference, this feature is an inheritance of the first
> implementation of the DSL that was without branches so just a linear
> sequence of steps and assumed that as example, you just want to deal with
> the individual items that are the result of the split.
>
>
>> And this is a bit "tricky" for new users to Camel DSL to learn.
>>
>> So I think maybe it's okay to not have the flow and keep the yaml dsl
>> as-is (although it can be verbose with those nested steps)
>>
>>
> Fine with me and if we'll find that having something like this in the
> future, we may introduce a dedicated "flow" definition.
>
>
>>
>> On Wed, Feb 24, 2021 at 9:16 AM Luca Burgazzoli 
>> wrote:
>> >
>> > Additional question: should we support "flow" like route definition ?
>> > To give an example of what a "flow" is, here a simple route that split
>> and
>> > process each item individually:
>> >
>> > - from:
>> > uri: "direct:route"
>> > steps:
>> >   - split:
>> >   tokenize: ","
>> >   steps:
>> > - to: "mock:split"
>> >
>> > A "flow" variant would be:
>> >
>> > - from:
>> > uri: "direct:route"
>> > steps:
>> >   - split:
>> >   tokenize: ","
>> >   - to: "mock:split"
>> >
>> > So in essence, if steps are not explicit configured on an OutputNode (in
>> > this case "split"), then such processor is the one to which each
>> subsequent
>> > steps is attached. This helps to mimics the Java DSL but at the same
>> time,
>> > it may be confusing so the new YAML DSL does not support this pattern
>> out
>> > of the box: should I enable it ?
>> >
>> > ---
>> > Luca Burgazzoli
>> >
>> >
>> > On Wed, Feb 24, 2021 at 7:09 AM Claus Ibsen 
>> wrote:
>> >
>> > > Hi Luca
>> > >
>> > >
>> > > On Tue, Feb 23, 2021 at 8:16 PM Luca Burgazzoli <
>> lburgazz...@gmail.com>
>> > > wrote:
>> > > >
>> > > > Hi,
>> > > >
>> > > > over the past weeks I've worked to clean up the YAML DSL I've
>> created for
>> > > > camel-k [1] which ended up in a complete rewrite [2].
>> > > >
>> > > > The new implementation is in large part auto generated out of the
>> camel
>> > > > model (with some minor manual adjustments), it does not use
>> reflection,
>> > > it is
>> > > > based on the SnakeYAML Engine [3] and it includes a much simpler
>> > > generator
>> > > > for the JSON schema as all the information are attached to the
>> generated
>> > > > code.
>> > > >
>> > > > The engine behind the DSL is pretty much stable and there are some
>> tasks
>> > > > I'd still have to do but as they are pretty much internal and may
>> require
>> > > > some change to the Camel model, I'd like to merge my work on Camel
>> as
>> > > soon
>> > > > as possible hence, I have some question about the process:
>> > > >
>> > >
>> >

Re: [HEADSUP] YAML DSL in Camel

[Luca Burgazzoli]

On Wed, Feb 24, 2021 at 9:33 AM Claus Ibsen  wrote:

> Hi
>
> Dont you have a "problem" with the flow style that you can't "end" the
> split and do something after it
>
> For example having a split in the middle, where a and b are outside
> the splitter then you can do in Java as
>
> from x
> to a
> split
> to sub 1
> to sub 2
> end
> to b
>

Yes absolutely and that's why I have not re-implemented it.
It also make the json schema validation a little weak as you cannot mark
steps as required.

Just for reference, this feature is an inheritance of the first
implementation of the DSL that was without branches so just a linear
sequence of steps and assumed that as example, you just want to deal with
the individual items that are the result of the split.


> And this is a bit "tricky" for new users to Camel DSL to learn.
>
> So I think maybe it's okay to not have the flow and keep the yaml dsl
> as-is (although it can be verbose with those nested steps)
>
>
Fine with me and if we'll find that having something like this in the
future, we may introduce a dedicated "flow" definition.


>
> On Wed, Feb 24, 2021 at 9:16 AM Luca Burgazzoli 
> wrote:
> >
> > Additional question: should we support "flow" like route definition ?
> > To give an example of what a "flow" is, here a simple route that split
> and
> > process each item individually:
> >
> > - from:
> > uri: "direct:route"
> > steps:
> >   - split:
> >   tokenize: ","
> >   steps:
> > - to: "mock:split"
> >
> > A "flow" variant would be:
> >
> > - from:
> > uri: "direct:route"
> > steps:
> >   - split:
> >   tokenize: ","
> >   - to: "mock:split"
> >
> > So in essence, if steps are not explicit configured on an OutputNode (in
> > this case "split"), then such processor is the one to which each
> subsequent
> > steps is attached. This helps to mimics the Java DSL but at the same
> time,
> > it may be confusing so the new YAML DSL does not support this pattern out
> > of the box: should I enable it ?
> >
> > ---
> > Luca Burgazzoli
> >
> >
> > On Wed, Feb 24, 2021 at 7:09 AM Claus Ibsen 
> wrote:
> >
> > > Hi Luca
> > >
> > >
> > > On Tue, Feb 23, 2021 at 8:16 PM Luca Burgazzoli  >
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > over the past weeks I've worked to clean up the YAML DSL I've
> created for
> > > > camel-k [1] which ended up in a complete rewrite [2].
> > > >
> > > > The new implementation is in large part auto generated out of the
> camel
> > > > model (with some minor manual adjustments), it does not use
> reflection,
> > > it is
> > > > based on the SnakeYAML Engine [3] and it includes a much simpler
> > > generator
> > > > for the JSON schema as all the information are attached to the
> generated
> > > > code.
> > > >
> > > > The engine behind the DSL is pretty much stable and there are some
> tasks
> > > > I'd still have to do but as they are pretty much internal and may
> require
> > > > some change to the Camel model, I'd like to merge my work on Camel as
> > > soon
> > > > as possible hence, I have some question about the process:
> > > >
> > >
> > > Yeah its great work and we should get it into Camel 3.9.
> > > This new DSL will also help us in the future to keep the DSL model
> > > more stable and useable for more languages.
> > >
> > >
> > > > - the engine leverages some new APIs from Java 11 (var is pretty
> useful
> > > for
> > > > code generation), I don't remember what was our plan to move Camel to
> > > Java
> > > > 11 so wonder if I need to migrate the code to Java 8 or if we'll
> move to
> > > > Java 11 soon
> > >
> > > Yes var is much greater for code generation. I hit roadblocks with the
> > > cimple code generator
> > > where using var would benefit greatly. And therefore the current
> > > implementation lacks some
> > > features that are in the regular simple language.
> > >
> > > About Java 11 then we have some components today that requires Java 11
> > > at runtime, like camel-joor.
> > > I am fine with 

Re: [HEADSUP] YAML DSL in Camel

[Luca Burgazzoli]

Additional question: should we support "flow" like route definition ?
To give an example of what a "flow" is, here a simple route that split and
process each item individually:

- from:
uri: "direct:route"
steps:
  - split:
  tokenize: ","
  steps:
- to: "mock:split"

A "flow" variant would be:

- from:
uri: "direct:route"
steps:
  - split:
  tokenize: ","
  - to: "mock:split"

So in essence, if steps are not explicit configured on an OutputNode (in
this case "split"), then such processor is the one to which each subsequent
steps is attached. This helps to mimics the Java DSL but at the same time,
it may be confusing so the new YAML DSL does not support this pattern out
of the box: should I enable it ?

---
Luca Burgazzoli


On Wed, Feb 24, 2021 at 7:09 AM Claus Ibsen  wrote:

> Hi Luca
>
>
> On Tue, Feb 23, 2021 at 8:16 PM Luca Burgazzoli 
> wrote:
> >
> > Hi,
> >
> > over the past weeks I've worked to clean up the YAML DSL I've created for
> > camel-k [1] which ended up in a complete rewrite [2].
> >
> > The new implementation is in large part auto generated out of the camel
> > model (with some minor manual adjustments), it does not use reflection,
> it is
> > based on the SnakeYAML Engine [3] and it includes a much simpler
> generator
> > for the JSON schema as all the information are attached to the generated
> > code.
> >
> > The engine behind the DSL is pretty much stable and there are some tasks
> > I'd still have to do but as they are pretty much internal and may require
> > some change to the Camel model, I'd like to merge my work on Camel as
> soon
> > as possible hence, I have some question about the process:
> >
>
> Yeah its great work and we should get it into Camel 3.9.
> This new DSL will also help us in the future to keep the DSL model
> more stable and useable for more languages.
>
>
> > - the engine leverages some new APIs from Java 11 (var is pretty useful
> for
> > code generation), I don't remember what was our plan to move Camel to
> Java
> > 11 so wonder if I need to migrate the code to Java 8 or if we'll move to
> > Java 11 soon
>
> Yes var is much greater for code generation. I hit roadblocks with the
> cimple code generator
> where using var would benefit greatly. And therefore the current
> implementation lacks some
> features that are in the regular simple language.
>
> About Java 11 then we have some components today that requires Java 11
> at runtime, like camel-joor.
> I am fine with the yaml dsl being Java 11 only. In the maven pom.xml
> we can make some way to skip this module if you use Java 8 compiler.
> And for releasing we can use Java 11 compiler with target 1.8 for all
> other modules, and then 1.11 for this module.
>
> > - the code generation is based on JavaPoet [4] and I have plans to
> migrate
> > to the camel own tool but since it does not affect the correctness of the
> > code, I think I could delay the migration to a later stage.
>
> Yeah that is okay as the code generator is a one process and part of
> building. the Camel project,
> and not for end users to run.
>
> > - I could make the YAML DSL part of a new camel-snakeyaml component but
> for
> > modularity, I wonder if we should introduce specific artifacts like
> > camel-dsl-yaml, camel-dsl-xml-io, etc.
> >
>
> Yes I would like to have this in its own module name.
> We use camel-endpointdsl and camel-componentdsl today, so it could
> also be named camel-yaml-dsl
>
>
>
> > Let me know,
> > Luca
> >
> > [1]
> >
> https://github.com/apache/camel-k-runtime/tree/master/camel-k-loader-yaml
> > [2] https://github.com/lburgazzoli/camel-yaml-dsl
> > [3] https://bitbucket.org/asomov/snakeyaml-engine/
> > [4] https://github.com/square/javapoet
> >
> >
> > ---
> > Luca Burgazzoli
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: [VOTE] Release Apache Camel-kafka-connector 0.8.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Tue, Feb 23, 2021 at 2:10 PM Jean-Baptiste Onofre 
wrote:

> +1 (binding)
>
> Regards
> JB
>
> > Le 23 févr. 2021 à 11:03, Andrea  a écrit :
> >
> > Hello all,
> >
> > This is a vote to release Apache Camel-kafka-connector 0.8.0
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1296
> >
> > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-kafka-connector.git;a=tag;h=refs/tags/camel-kafka-connector-0.8.0
> >
> > Aligned with camel 3.8.0
> >
> https://github.com/apache/camel-kafka-connector/issues?q=is%3Aissue+milestone%3A0.8.0+is%3Aclosed
> >
> > Please test this release candidate and cast your vote.
> > [ ] +1 Release the binary as  Apache Camel-kafka-connector 0.8.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 48 hours.
> >
> > Thanks,
> > Andrea.
>
>

[HEADSUP] YAML DSL in Camel

[Luca Burgazzoli]

Hi,

over the past weeks I've worked to clean up the YAML DSL I've created for
camel-k [1] which ended up in a complete rewrite [2].

The new implementation is in large part auto generated out of the camel
model (with some minor manual adjustments), it does not use reflection, it is
based on the SnakeYAML Engine [3] and it includes a much simpler generator
for the JSON schema as all the information are attached to the generated
code.

The engine behind the DSL is pretty much stable and there are some tasks
I'd still have to do but as they are pretty much internal and may require
some change to the Camel model, I'd like to merge my work on Camel as soon
as possible hence, I have some question about the process:

- the engine leverages some new APIs from Java 11 (var is pretty useful for
code generation), I don't remember what was our plan to move Camel to Java
11 so wonder if I need to migrate the code to Java 8 or if we'll move to
Java 11 soon
- the code generation is based on JavaPoet [4] and I have plans to migrate
to the camel own tool but since it does not affect the correctness of the
code, I think I could delay the migration to a later stage.
- I could make the YAML DSL part of a new camel-snakeyaml component but for
modularity, I wonder if we should introduce specific artifacts like
camel-dsl-yaml, camel-dsl-xml-io, etc.

Let me know,
Luca

[1]
https://github.com/apache/camel-k-runtime/tree/master/camel-k-loader-yaml
[2] https://github.com/lburgazzoli/camel-yaml-dsl
[3] https://bitbucket.org/asomov/snakeyaml-engine/
[4] https://github.com/square/javapoet


---
Luca Burgazzoli

Re: [VOTE] Release Apache Camel Quarkus 1.7.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Fri, Feb 19, 2021 at 12:41 PM Omar Al-Safi  wrote:

> +1 (binding)
>
> Thanks
>
> On Fri, Feb 19, 2021 at 12:09 PM Otavio Rodolfo Piske <
> angusyo...@gmail.com>
> wrote:
>
> > +1 (non-binding)
> >
> > Thanks!
> >
> > On Fri, Feb 19, 2021 at 12:03 PM Claus Ibsen 
> > wrote:
> >
> > > +1 (binding)
> > >
> > > On Fri, Feb 19, 2021 at 10:32 AM Peter Palaga 
> > wrote:
> > > >
> > > > Hi,
> > > >
> > > > This is a vote to release Apache Camel Quarkus 1.7.0.
> > > >
> > > > Highlights:
> > > >
> > > > * Camel 3.8.0
> > > > * Quarkus 1.12.0.Final
> > > > * Fixed issues:
> > > > https://github.com/apache/camel-quarkus/milestone/11?closed=1
> > > > * Known issues:
> > > >* https://github.com/apache/camel-quarkus/issues/2207
> > > >* https://github.com/apache/camel-quarkus/issues/2253
> > > > * All commits:
> > > https://github.com/apache/camel-quarkus/compare/1.6.0...1.7.0
> > > > Staging repository:
> > > >
> > > >
> https://repository.apache.org/content/repositories/orgapachecamel-1295
> > > >
> > > > Tag: https://github.com/apache/camel-quarkus/releases/tag/1.7.0
> > > >
> > > > Source release package:
> > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1295/org/apache/camel/quarkus/camel-quarkus/1.7.0/camel-quarkus-1.7.0-src.zip
> > > >
> > > > Please test this release candidate and cast your vote.
> > > >
> > > > [ ] +1 Release the binary as Apache Camel Quarkus 1.7.0
> > > > [ ] -1 Veto the release (provide specific comments)
> > > >
> > > > The vote is open for at least 72 hours.
> > > >
> > > > Many thanks to all contributors!
> > > >
> > > > -- Peter
> > > >
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -
> > > http://davsclaus.com @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >
> >
> >
> > --
> > Otavio R. Piske
> > http://orpiske.net
> >
>

Re: [VOTE] Release Apache Camel K 1.3.1

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Feb 1, 2021 at 5:02 PM Zoran Regvart  wrote:

> +1 (binding)
>
> Thanks Nicola!
>
> On Mon, Feb 1, 2021 at 12:55 PM Nicola Ferraro 
> wrote:
> >
> > Hello all:
> >
> > This is a vote to release Apache Camel K 1.3.1.
> >
> > This release fixes general bugs and improves compatibility with recent
> > versions of Knative. More details on the release notes:
> > https://github.com/apache/camel-k/issues/1966#issuecomment-770748644
> >
> > Camel K staging repository:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k/1.3.1/
> > Camel K Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.3.1
> >
> > Staging container image repository:
> https://hub.docker.com/r/camelk/camel-k
> > /tags
> >
> > It's possible to install all staging artifacts with a single command:
> > kamel install --operator-image=camelk/camel-k:1.3.1 --olm=false
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel K 1.3.1
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Nicola Ferraro
>
>
>
> --
> Zoran Regvart
>

Re: Deprecating Camel-AWS

[Luca Burgazzoli]

+1

---
Luca Burgazzoli


On Fri, Jan 29, 2021 at 7:10 AM Claus Ibsen  wrote:

> Fine with me
>
> On Fri, Jan 29, 2021 at 6:58 AM Andrea Cosentino 
> wrote:
> >
> > Hello,
> >
> > I would like to deprecate the camel-aws-* components to focus on AWS2 and
> > maybe renaming them. My proposal is to deprecate the components for 3.8.x
> > (since we want to release on the 5th Feb week) and remove them in 3.9.
> For
> > the 3.10.x LTS we can rename the v2 version to camel-aws again and add
> > information in the documentation.
> >
> > What do you think?
> >
> > Thanks.
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: [VOTE] Release Apache Camel Quarkus 1.6.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Jan 18, 2021 at 4:29 PM Jean-Baptiste Onofre 
wrote:

> +1 (binding)
>
> Regards
> JB
>
> > Le 15 janv. 2021 à 11:25, Peter Palaga  a écrit :
> >
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 1.6.0.
> >
> > Highlights:
> >
> > * Quarkus 1.11.0.Final
> > * Java 11+ required (following the same requirement by Quarkus)
> > * Fixed issues:
> https://github.com/apache/camel-quarkus/milestone/10?closed=1
> > * All commits:
> https://github.com/apache/camel-quarkus/compare/1.5.0...1.6.0
> >
> > Staging repository:
> >
> > https://repository.apache.org/content/repositories/orgapachecamel-1275
> >
> > Tag: https://github.com/apache/camel-quarkus/releases/tag/1.6.0
> >
> > Source release package:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1275/org/apache/camel/quarkus/camel-quarkus/1.6.0/camel-quarkus-1.6.0-src.zip
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel Quarkus 1.6.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Many thanks to all contributors!
> >
> > -- Peter
> >
>
>

Re: [VOTE] Release Apache Camel K 1.3.0 and Runtime 1.6.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Wed, Dec 23, 2020 at 10:13 AM Alexandre Gallice 
wrote:

> +1 (binding)
>
> Alex
>
> On Wed, Dec 23, 2020 at 7:04 AM Jean-Baptiste Onofre 
> wrote:
>
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > > Le 22 déc. 2020 à 18:47, Nicola Ferraro  a écrit
> :
> > >
> > > Hello all:
> > >
> > > This is a vote to release Apache Camel K 1.3.0 and Camel K Runtime
> 1.6.0.
> > >
> > > This release contains many changes in the runtime (Quarkus is the only
> > > supported runtime) and includes many new features. More details in the
> > > release notes:
> > > https://github.com/apache/camel-k/issues/1867#issuecomment-749681448
> > >
> > > Runtime staging repository:
> > > https://repository.apache.org/content/repositories/orgapachecamel-1274
> > > Runtime Tag:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-project-1.6.0
> > >
> > > Camel K staging repository:
> > > https://dist.apache.org/repos/dist/dev/camel/camel-k/1.3.0/
> > > Camel K Tag:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.3.0
> > >
> > > Staging container image repository:
> > https://hub.docker.com/r/camelk/camel-k
> > > /tags
> > >
> > > It's possible to install all staging artifacts with a single command:
> > > kamel install --operator-image=camelk/camel-k:1.3.0 --maven-repository=
> > > https://repository.apache.org/content/repositories/orgapachecamel-1274
> > > --olm=false
> > >
> > > Please test this release candidate and cast your vote.
> > >
> > > [ ] +1 Release the binary as Apache Camel K 1.3.0 and Apache Camel K
> > Runtime
> > > 1.6.0
> > > [ ] -1 Veto the release (provide specific comments)
> > >
> > > The vote is open for at least 72 hours (maybe more this time :D).
> > >
> > > Here's my +1.
> > >
> > > Thanks,
> > > Nicola Ferraro
> >
> >
>

Re: [VOTE] Release Apache Camel Quarkus 1.5.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Tue, Dec 15, 2020 at 8:54 AM Jean-Baptiste Onofre 
wrote:

> +1 (binding)
>
> Regards
> JB
>
> > Le 14 déc. 2020 à 23:12, Peter Palaga  a écrit :
> >
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 1.5.0.
> >
> > Highlights:
> >
> > * Camel 3.7.0
> > * Fixed issues:
> https://github.com/apache/camel-quarkus/milestone/9?closed=1
> > * All commits:
> https://github.com/apache/camel-quarkus/compare/1.4.0...1.5.0
> >
> > Staging repository:
> >
> > https://repository.apache.org/content/repositories/orgapachecamel-1266
> (depends on Camel 3.7.0 staging repository; to test use this settings file
> https://github.com/apache/camel-quarkus/blob/1.5.0/settings-camel-3.7.0.xml
> )
> >
> > Tag: https://github.com/apache/camel-quarkus/releases/tag/1.5.0
> >
> > Source release package:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1266/org/apache/camel/quarkus/camel-quarkus/1.5.0/camel-quarkus-1.5.0-src.zip
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel Quarkus 1.5.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Many thanks to all contributors!
> >
> > -- Peter
> >
>
>

Re: [VOTE] Release Apache Camel 3.7.0 with Spring Boot and Karaf Support Projects

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Dec 14, 2020 at 9:34 AM Babak Vahdat 
wrote:

> +1 (binding)
>
> Thanks,
> Babak
>
> > On 13 Dec 2020, at 09:15, Gregor Zurowski 
> wrote:
> >
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 3.7.0 (with Apache Camel Spring
> > Boot and Apache Camel Karaf), a new minor release with 185
> > improvements and fixes.
> >
> > Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12349250=12311220
> >
> > == Apache Camel 3.7.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1263/
> >
> > Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1263/org/apache/camel/apache-camel/3.7.0/
> >
> > Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.7.0
> >
> > == Apache Camel Spring Boot 3.7.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1264/
> >
> > Tag:
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.7.0
> >
> > == Apache Camel Karaf 3.7.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1265/
> >
> > Tag:
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.7.0
> >
> > Please test this release candidate and cast your vote.
> > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > Karaf 3.7.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
>
>

Re: [VOTE] Release Apache Camel K 1.2.1

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Nov 23, 2020 at 9:33 PM Alexandre Gallice 
wrote:

> +1 (binding)
>
> Well done :)
> Alex
>
> On Mon, Nov 23, 2020 at 6:46 PM Andrea Cosentino
>  wrote:
>
> > +1(binding)
> >
> > Thanks!
> >
> > --
> > Andrea Cosentino
> > --
> > Apache Camel PMC Chair
> > Apache Karaf Committer
> > Apache Servicemix PMC Member
> > Email: ancosen1...@yahoo.com
> > Twitter: @oscerd2
> > Github: oscerd
> >
> >
> >
> >
> >
> >
> > On Monday, November 23, 2020, 05:27:28 PM GMT+1, Nicola Ferraro <
> > nferr...@apache.org> wrote:
> >
> >
> >
> >
> >
> > Hello all:
> >
> > This is a vote to release Apache Camel K 1.2.1.
> >
> > This release contains mainly bug fixes on Kamelets usage. More details on
> > the release notes:
> > https://github.com/apache/camel-k/issues/1823#issuecomment-732243417
> >
> > Camel K staging repository:
> https://dist.apache.org/repos/dist/dev/camel/
> > camel-k/1.2.1/
> > <https://dist.apache.org/repos/dist/dev/camel/camel-k/1.2.1/>
> > Camel K Tag: https://gitbox.apache.org/repos/asf?p=camel-k
> > .git;a=shortlog;h=refs/tags/v1.2.1
> >
> > Staging container image repository:
> > https://hub.docker.com/r/camelk/camel-k
> > /tags
> >
> > It's possible to install all staging artifacts with a single command:
> > kamel install --operator-image=camelk/camel-k:1.2.1 --olm=false
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel K 1.2.1
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Nicola Ferraro
> >
>

Re: [VOTE] Release Apache Camel Quarkus 1.4.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Fri, Nov 20, 2020 at 6:48 AM Andrea Cosentino  wrote:

> +1 (binding)
>
> Thanks Alex
>
> Il giorno gio 19 nov 2020 alle ore 18:49 Alexandre Gallice <
> aldettin...@gmail.com> ha scritto:
>
> > Hi Cameleers,
> >
> > This is a vote to release Apache Camel Quarkus 1.4.0.
> >
> > The main difference against Camel Quarkus 1.3.0 are listed below:
> >
> > * Upgraded to Quarkus 1.10.0.Final
> > * Addition of native support for 7 extensions
> > * Bug fixes and improvements
> > * Fixed issues:
> > https://github.com/apache/camel-quarkus/milestone/8?closed=1
> > * All commits:
> > https://github.com/apache/camel-quarkus/compare/1.3.0...1.4.0
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1261
> >
> > Tag: https://github.com/apache/camel-quarkus/releases/tag/1.4.0
> >
> > Source release package:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1261/org/apache/camel/quarkus/camel-quarkus/1.4.0/camel-quarkus-1.4.0-src.zip
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel Quarkus 1.4.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > I'll close the vote 72 hours from now.
> >
> > Kudos to all contributors !
> > Alex
> >
>

Re: [VOTE] Release Apache Camel 3.6.0 with Spring Boot and Karaf Support Projects

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Oct 19, 2020 at 10:27 AM Zoran Regvart  wrote:

> +1 (binding)
>
> Thanks Gregor!
>
> zoran
>
> On Mon, Oct 19, 2020 at 7:53 AM Jean-Baptiste Onofre 
> wrote:
> >
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > > Le 17 oct. 2020 à 15:22, Gregor Zurowski  a
> écrit :
> > >
> > > Hi Everyone:
> > >
> > > This is a vote to release Apache Camel 3.6.0 (with Apache Camel Spring
> > > Boot and Apache Camel Karaf), a new minor release with 151
> > > improvements and fixes.
> > >
> > > Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12348664=12311220
> > >
> > > == Apache Camel 3.6.0 ==
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1254/
> > >
> > > Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1254/org/apache/camel/apache-camel/3.6.0/
> > >
> > > Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.6.0
> > >
> > > == Apache Camel Spring Boot 3.6.0 ==
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1255/
> > >
> > > Tag:
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.6.0
> > >
> > > == Apache Camel Karaf 3.6.0 ==
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1256/
> > >
> > > Tag:
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.6.0
> > >
> > > Please test this release candidate and cast your vote.
> > > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > > Karaf 3.6.0
> > > [ ] -1 Veto the release (provide specific comments)
> > >
> > > The vote is open for at least 72 hours.
> > >
> > > Thanks,
> > > Gregor
> >
>
>
> --
> Zoran Regvart
>

Re: [VOTE] Release Apache Camel Quarkus 1.3.0

[Luca Burgazzoli]

+1 (binding)

Thx Peter


---
Luca Burgazzoli


On Mon, Oct 19, 2020 at 10:28 AM Zoran Regvart  wrote:

> +1 (binding)
>
> Thanks Peter for a super prompt release :)
>
> zoran
>
> On Sat, Oct 17, 2020 at 4:06 PM Peter Palaga  wrote:
> >
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 1.3.0.
> >
> > The main difference against Camel Quarkus 1.2.0, that is under vote too,
> > is the upgrade to Camel 3.6.0. The release branch was tested against
> > Camel 3.6.0 staging repo
> > https://repository.apache.org/content/repositories/orgapachecamel-1254
> >
> > Highlights:
> >
> > * Camel 3.6.0
> > * Fixed issues: https://github.com/apache/camel-quarkus/milestone/7
> > * All commits:
> https://github.com/apache/camel-quarkus/compare/1.2.0...1.3.0
> >
> > Staging repository:
> >
> > https://repository.apache.org/content/repositories/orgapachecamel-1257
> >
> > Tag: https://github.com/apache/camel-quarkus/releases/tag/1.3.0
> >
> > Source release package:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1257/org/apache/camel/quarkus/camel-quarkus/1.3.0/camel-quarkus-1.3.0-src.zip
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel Quarkus 1.3.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > I'll close the vote 72 hours from now, right after the parallel vote for
> > Camel 3.6.0 is closed.
> >
> > Many thanks to all contributors!
> >
> > -- Peter
> >
>
>
> --
> Zoran Regvart
>

Re: [VOTE] Release Apache Camel Quarkus 1.2.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Thu, Oct 15, 2020 at 1:40 PM Peter Palaga  wrote:

> On 15/10/2020 13:36, Peter Palaga wrote:
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 1.2.0.
> >
> > Highlights:
> >
> > * Quarkus 1.9.0.Final
> > * We are approaching
>
> ... the milestone of covering 100% of Camel components (party in JVM mode).
>
> > * Fixed issues: https://github.com/apache/camel-quarkus/milestone/6
> > * All commits:
> > https://github.com/apache/camel-quarkus/compare/1.1.0...1.2.0
> >
> > Staging repository:
> >
> > https://repository.apache.org/content/repositories/orgapachecamel-1253
> >
> > Tag:
> >
> >
> https://gitbox.apache.org/repos/asf?p=camel-quarkus.git;a=commit;h=7bda77c3df151b8fc165efb224136bb5f3b0b6c5
> >
> >
> > Source release package:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1253/org/apache/camel/quarkus/camel-quarkus/1.2.0/camel-quarkus-1.2.0-src.zip
> >
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel Quarkus 1.2.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Many thanks to all contributors!
> >
> > -- Peter
>
>

Re: [VOTE] Release Apache Camel K 1.2.0 and Runtime 1.5.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Thu, Oct 8, 2020 at 7:36 PM Nicola Ferraro  wrote:

> Hello all:
>
> This is a vote to release Apache Camel K 1.2.0 and Camel K Runtime 1.5.1.
>
> This release contains many changes in the runtime and includes many new
> features, such as support for Kamelets. More details on the changelog:
> https://github.com/apache/camel-k/blob/master/CHANGELOG.md#unreleased
>
> Runtime staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1251
> Runtime Tag:
>
> https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-parent-1.5.0
>
> Camel K staging repository:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/1.2.0/
> Camel K Tag:
>
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.2.0
>
> Staging container image repository:
> https://hub.docker.com/r/camelk/camel-k
> /tags
>
> It's possible to install all staging artifacts with a single command:
> kamel install --operator-image=camelk/camel-k:1.2.0 --maven-repository=
> https://repository.apache.org/content/repositories/orgapachecamel-1251
>  --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel K 1.2.0 and Apache Camel K
> Runtime
> 1.5.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Nicola Ferraro
>

[HEADS UP] deploy to ASF snapshot repo from GitHub Actions

[Luca Burgazzoli]

Hi,

now that https://issues.apache.org/jira/browse/INFRA-20846 has been
implemented, you can publish snapshots to the ASF repo from GitHub Actions.

The first implementation has been done for the camel-k-runtime repo:

-
https://github.com/apache/camel-k-runtime/blob/master/.github/workflows/ci-build.yml#L117-L131
-
https://github.com/apache/camel-k-runtime/blob/master/.github/asf-deploy-settings.xml

---
Luca Burgazzoli

Re: [VOTE] Release Apache Camel 3.4.4 (LTS)

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Thu, Sep 24, 2020 at 8:54 AM Francois Papon 
wrote:

> +1 (non-binding)
>
> Thanks!
>
> regards,
>
> François
> fpa...@apache.org
>
> Le 23/09/2020 à 15:35, Gregor Zurowski a écrit :
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 3.4.4, a new patch release for
> > the 3.4.x LTS branch with 31 improvements and fixes.
> >
> > Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12348674=12311211
> >
> > == Apache Camel 3.4.4 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1248/
> >
> > Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1248/org/apache/camel/apache-camel/3.4.4/
> >
> > Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.4.4
> >
> > == Apache Camel Spring Boot 3.4.4 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1249/
> >
> > Tag:
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.4.4
> >
> > == Apache Camel Karaf 3.4.4 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1250/
> >
> > Tag:
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.4.4
> >
> > Please test this release candidate and cast your vote.
> > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > Karaf 3.4.4
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
>

Re: [Discussion] Sharing test containers/infrastructure among projects

[Luca Burgazzoli]

Hi Otavio,

as you know, big +1 on that idea.

As a strategy I'm thinking about:

1. try to contribute to TestContainers to make it easy to configure some
common tasks the implementations they ship and eventually provide some new
ones.
2. create some new modules, don't ask me for a name, with the core
infrastructure code and some specific impl.
3. see if we can easily hook such service in the camel-test* and eventually
deprecate camel-testcontainers*

---
Luca Burgazzoli


On Fri, Sep 11, 2020 at 3:49 PM Otavio Rodolfo Piske 
wrote:

> Hello everyone!
>
> Luca B, Andrea T. and I had a brief discussion / brainstorm today about
> adjusting part of our testing infrastructure code so that it is easier for
> all the projects to levage testing bits used throughout the project. The
> issue that led to this idea can be found here [1].
>
> As it is common these days, a lot of projects use TestContainers [2] to set
> up the test infrastructure required for the tests to run. This is how the
> integration tests for the Camel Kafka Connector work [3].
>
> In the Camel Kafka Connector, the test infrastructure contains
> "AbstractServices". They can be resolved either to containers managed by
> TestContainers or remote instances of the services. These services are
> injected into the test code using JUnit 5 extensions. It uses a generic
> approach and it is not tightly coupled to Kafka Connect or the Camel Kafka
> Connector project.
>
> In more concrete terms, the idea is to make this test infrastructure more
> easily accessible for other projects. This would involve moving this code
> to another project (Camel? Where?), adjusting the few parts that may be
> coupled (if any at all) and moving the part of the testing documentation
> [4] (check the "Simulating the Test Infrastructure" part).
>
> A few potential benefits of this idea are reducing our effort in handling
> the test infrastructure throughout the code base and simplifying how we
> assert the behavior of each project for each infrastructure (ie.: we may
> want to make sure that components behave the same way across all projects).
>
> What do you think?
>
> 1. https://github.com/apache/camel-quarkus/issues/1783
> 2. https://www.testcontainers.org/
> 3. https://github.com/apache/camel-kafka-connector/tree/master/tests
> 4. https://camel.apache.org/camel-kafka-connector/latest/testing.html
>
> Kind regards
> --
> Otavio R. Piske
> http://orpiske.net
>

[HEADS UP] The official Camel chat is now on Zulip

[Luca Burgazzoli]

Hello,

As discussed [1] and voted [2] on the dev mailing list, the official chat
for Apache Camel is now on Zulip [3].

The rooms hosted on gitter [4][5][6][7] are still active but won't be used
anymore soon so it is recommended to switch to Zulip.

Regards,
Luca

[1]
https://lists.apache.org/thread.html/rfa0b6020b0bd69115e28487633e2ab0059431ba8d9a3246d7780aedd%40%3Cdev.camel.apache.org%3E
[2]
https://lists.apache.org/thread.html/r6e4738b11c7b1c23697039bfeb6455db57fafe2e0fb1a8feb1dee7c1%40%3Cdev.camel.apache.org%3E
[3] https://camel.zulipchat.com/
[4] https://gitter.im/apache/apache-camel
[5] https://gitter.im/apache/camel-k
[6] https://gitter.im/apache/camel-quarkus
[7] https://gitter.im/apache/camel-kafka-connector

---
Luca Burgazzoli

Re: [VOTE] Switch from Gitter to Zulip as official Camel chatroom

[Luca Burgazzoli]

Hi,

I've created a brand new Camel Zulip organization here:
https://camel.zulipchat.com
I've asked to upgrade it to the standard open source profile, I'll post
here when it will be ready but in the meantime you can join the new
organization.
I'll send an email to the mailing lists later today.

I'm now the only admin of that organization but I'll give admin rights to
every member of the Camel PMC so PMC members, ping me once joined so I know
what is the account associated with you.

Luca

---
Luca Burgazzoli


On Tue, Sep 8, 2020 at 9:39 AM Luca Burgazzoli 
wrote:

> Thanks for your participation in this vote.
>
> The vote passes with the following results:
>
> +1 : 9 (Andrea Cosentino, Nicola Ferraro, Otavio Rodolfo Piske, Djordje
> Bajić, Claus Ibsen, Dmitry Volodin, Peter Palaga, Ioannis Polyzos, Omar
> Al-Safi)
> +0 : 1 (Jean-Baptiste Onofre)
>
> I am going to create an official organization camel.zulipchat.com
>
> ---
> Luca Burgazzoli
>
>
> On Mon, Sep 7, 2020 at 10:19 AM Omar Al-Safi  wrote:
>
>> +1
>>
>> On Mon, Aug 31, 2020 at 11:39 PM Ioannis Polyzos 
>> wrote:
>>
>> > +1
>> >
>> > On Mon, 31 Aug 2020, 07:45 Luca Burgazzoli, 
>> wrote:
>> >
>> > > Hi,
>> > >
>> > > This is a vote to switch the official Camel chatroom from Gitter [1]
>> to
>> > > Zulip [2].
>> > >
>> > > For detail about the reason for the switch and discussion about
>> > > alternatives, please see the related thread on the @dev mailing list
>> > [3]. A
>> > > Zulip test instance you can join using GitHub, GitLab, Google or plain
>> > mail
>> > > is available [4], feel free to plain with it while the vote is open.
>> > >
>> > > [ ] +1 To switch from Gitter to Zulip
>> > > [ ] -1 To Veto the switch (provide specific comments)
>> > >
>> > > The vote is open for at least 72 hours.
>> > >
>> > > Thank you for your participation,
>> > > Luca
>> > >
>> > > [1] https://gitter.im
>> > > [2] https://zulipchat.com/
>> > > [3]
>> > >
>> https://mail-archives.apache.org/mod_mbox/camel-dev/202008.mbox/browser
>> > > [4] https://camel-test.zulipchat.com
>> > >
>> > >
>> > > ---
>> > > Luca Burgazzoli
>> > >
>> >
>>
>

Re: [VOTE] Release Apache Camel K 1.1.1

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Fri, Sep 11, 2020 at 2:10 PM Claus Ibsen  wrote:

> +1 (binding)
>
> On Fri, Sep 11, 2020 at 1:01 PM Nicola Ferraro 
> wrote:
> >
> > Hello all:
> >
> > This is a vote to release Apache Camel K 1.1.1.
> >
> > This is a patch release mainly due to fix incompatibility issues with the
> > latest version of Knative. More details on the release notes:
> > https://github.com/apache/camel-k/issues/1700#issue-699125934
> >
> > Camel K staging repository:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k/1.1.1/
> > Camel K Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.1.1
> >
> > Staging container image repository:
> https://hub.docker.com/r/camelk/camel-k
> > /tags
> >
> > It's possible to install all staging artifacts with a single command:
> > kamel install --operator-image=camelk/camel-k:1.1.1 --olm=false
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel K 1.1.1
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Nicola Ferraro
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: [VOTE] Release Apache Camel Quarkus 1.1.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Wed, Sep 9, 2020 at 7:43 PM James Netherton 
wrote:

> Hi,
>
> This is a vote to release Apache Camel Quarkus 1.1.0.
>
> Highlights:
>
> * Based on Camel 3.5.0
> * Quarkus 1.8.0.Final
> * Fixed issues:
> https://github.com/apache/camel-quarkus/milestone/5?closed=1
>
> Staging repository:
>
> https://repository.apache.org/content/repositories/orgapachecamel-1247
>
> Tag:
>
>
> https://gitbox.apache.org/repos/asf?p=camel-quarkus.git;a=commit;h=81cd22d592affd8305eaeb96535e51e90b1cb888
>
> Source release package:
>
>
> https://repository.apache.org/content/repositories/orgapachecamel-1247/org/apache/camel/quarkus/camel-quarkus/1.1.0/camel-quarkus-1.1.0-src.zip
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel Quarkus 1.1.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> --
> James
>

Re: [VOTE] Release Apache Camel-kafka-connector 0.5.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Wed, Sep 9, 2020 at 3:27 PM Omar Al-Safi  wrote:

> +1 (binding)
>
> Thank you Andrea!
>
> On Wed, Sep 9, 2020 at 3:08 PM Andrea Cosentino  wrote:
>
> > +1 (binding)
> >
> > Thanks for the release Andrea
> >
> > Il giorno mer 9 set 2020 alle ore 14:35 Andrea  ha
> > scritto:
> >
> > > Hello all,
> > >
> > > This is a vote to release Apache Camel-kafka-connector 0.5.0
> > >
> > > Staging repository:
> > > https://repository.apache.org/content/repositories/orgapachecamel-1246
> > >
> > > Tag:
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=camel-kafka-connector.git;a=tag;h=refs/tags/camel-kafka-connector-0.5.0
> > >
> > > This release aligns to camel 3.5.0, add some profiling capabilities in
> > > itests on top of the usual bugfixing. You can see the complete
> changelog
> > > here:
> > >
> >
> https://github.com/apache/camel-kafka-connector/blob/master/CHANGELOG.md#camel-kafka-connector-050-2020-09-08
> > >
> > > Please test this release candidate and cast your vote.
> > > [ ] +1 Release the binary as  Apache Camel-kafka-connector 0.5.0
> > > [ ] -1 Veto the release (provide specific comments)
> > >
> > > The vote is open for at least 48 hours.
> > >
> > > Thanks,
> > > Andrea.
> > >
> >
>

Re: [VOTE] Switch from Gitter to Zulip as official Camel chatroom

[Luca Burgazzoli]

Thanks for your participation in this vote.

The vote passes with the following results:

+1 : 9 (Andrea Cosentino, Nicola Ferraro, Otavio Rodolfo Piske, Djordje
Bajić, Claus Ibsen, Dmitry Volodin, Peter Palaga, Ioannis Polyzos, Omar
Al-Safi)
+0 : 1 (Jean-Baptiste Onofre)

I am going to create an official organization camel.zulipchat.com

---
Luca Burgazzoli


On Mon, Sep 7, 2020 at 10:19 AM Omar Al-Safi  wrote:

> +1
>
> On Mon, Aug 31, 2020 at 11:39 PM Ioannis Polyzos 
> wrote:
>
> > +1
> >
> > On Mon, 31 Aug 2020, 07:45 Luca Burgazzoli, 
> wrote:
> >
> > > Hi,
> > >
> > > This is a vote to switch the official Camel chatroom from Gitter [1] to
> > > Zulip [2].
> > >
> > > For detail about the reason for the switch and discussion about
> > > alternatives, please see the related thread on the @dev mailing list
> > [3]. A
> > > Zulip test instance you can join using GitHub, GitLab, Google or plain
> > mail
> > > is available [4], feel free to plain with it while the vote is open.
> > >
> > > [ ] +1 To switch from Gitter to Zulip
> > > [ ] -1 To Veto the switch (provide specific comments)
> > >
> > > The vote is open for at least 72 hours.
> > >
> > > Thank you for your participation,
> > > Luca
> > >
> > > [1] https://gitter.im
> > > [2] https://zulipchat.com/
> > > [3]
> > >
> https://mail-archives.apache.org/mod_mbox/camel-dev/202008.mbox/browser
> > > [4] https://camel-test.zulipchat.com
> > >
> > >
> > > ---
> > > Luca Burgazzoli
> > >
> >
>

Re: [VOTE] Release Apache Camel 3.5.0 with Spring Boot and Karaf Support Projects

[Luca Burgazzoli]

+1 (binding) Tested with camle-k-runtime

---
Luca Burgazzoli


On Wed, Sep 2, 2020 at 3:20 PM Otavio Rodolfo Piske 
wrote:

> +1
>
> Thanks!!!
>
> On Wed, Sep 2, 2020 at 9:52 AM Alex Dettinger 
> wrote:
>
> > +1 (binding)
> >
> > Well done Gregor :)
> > Alex
> >
> > On Wed, Sep 2, 2020 at 8:24 AM Francois Papon <
> > francois.pa...@openobject.fr>
> > wrote:
> >
> > > +1 (non-binding)
> > >
> > > Thanks!
> > >
> > > regards,
> > >
> > > François
> > > fpa...@apache.org
> > >
> > > Le 01/09/2020 à 16:59, Gregor Zurowski a écrit :
> > > > Hi Everyone:
> > > >
> > > > This is a vote to release Apache Camel 3.5.0 (with Apache Camel
> Spring
> > > > Boot and Apache Camel Karaf), a new minor release with 240
> > > > improvements and fixes.
> > > >
> > > > Release notes:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12348299=12311220
> > > >
> > > > == Apache Camel 3.5.0 ==
> > > >
> > > > Staging repository:
> > > >
> > https://repository.apache.org/content/repositories/orgapachecamel-1243/
> > > >
> > > > Tarballs:
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1243/org/apache/camel/apache-camel/3.5.0/
> > > >
> > > > Tag:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.5.0
> > > >
> > > > == Apache Camel Spring Boot 3.5.0 ==
> > > >
> > > > Staging repository:
> > > >
> > https://repository.apache.org/content/repositories/orgapachecamel-1244/
> > > >
> > > > Tag:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.5.0
> > > >
> > > > == Apache Camel Karaf 3.5.0 ==
> > > >
> > > > Staging repository:
> > > >
> > https://repository.apache.org/content/repositories/orgapachecamel-1245/
> > > >
> > > > Tag:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.5.0
> > > >
> > > > Please test this release candidate and cast your vote.
> > > > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and
> Camel
> > > > Karaf 3.5.0
> > > > [ ] -1 Veto the release (provide specific comments)
> > > >
> > > > The vote is open for at least 72 hours.
> > > >
> > > > Thanks,
> > > > Gregor
> > >
> >
>
>
> --
> Otavio R. Piske
> http://orpiske.net
>

[VOTE] Switch from Gitter to Zulip as official Camel chatroom

[Luca Burgazzoli]

Hi,

This is a vote to switch the official Camel chatroom from Gitter [1] to
Zulip [2].

For detail about the reason for the switch and discussion about
alternatives, please see the related thread on the @dev mailing list [3]. A
Zulip test instance you can join using GitHub, GitLab, Google or plain mail
is available [4], feel free to plain with it while the vote is open.

[ ] +1 To switch from Gitter to Zulip
[ ] -1 To Veto the switch (provide specific comments)

The vote is open for at least 72 hours.

Thank you for your participation,
Luca

[1] https://gitter.im
[2] https://zulipchat.com/
[3] https://mail-archives.apache.org/mod_mbox/camel-dev/202008.mbox/browser
[4] https://camel-test.zulipchat.com


---
Luca Burgazzoli

Re: Alternatives to gitter

[Luca Burgazzoli]

Hi,

Should we start an official vote ?

---
Luca Burgazzoli


On Thu, Aug 27, 2020 at 4:08 PM Omar Al-Safi  wrote:

> I'd also give my vote on this:
>
> +1 zulip
> -1 gitter
> 0 slack
>
> Regards
>
> On Thu, Aug 27, 2020 at 1:40 PM Claus Ibsen  wrote:
>
> > Hi
> >
> > Thanks for the zulip testing experience.
> >
> > +1 for zulip
> > -1 for slack
> > 0 for staying on gitter
> >
> >
> >
> > On Fri, Aug 21, 2020 at 12:16 PM Luca Burgazzoli 
> > wrote:
> > >
> > > So I've created a new Zulip organization for testing purposes here:
> > > https://camel-test.zulipchat.com (I've named it camel-test as there's
> an
> > > option to import gitter chats but can be done only for new
> organization)
> > > Anyone should be able to join using github/gitlab/google, by mail or
> with
> > > an invitation.
> > >
> > > I've also had some discussion with the Zulip team as well as other
> teams
> > > using Zulip and I can confirm that it is possible to request a standard
> > > plan for open source so we can get rid of the message history issue.
> > >
> > > ---
> > > Luca Burgazzoli
> > >
> > >
> > > On Fri, Aug 21, 2020 at 11:22 AM Zoran Regvart 
> > wrote:
> > >
> > > > Never mind, found the answer in the second link you posted:
> > > >
> > > > https://zulipchat.com/for/open-source/
> > > >
> > > > “Free hosting at zulip.com.
> > > > The hosting is supported by (and is identical to) zulip.com’s
> > commercial
> > > > offerings. This offer extends to any community involved in supporting
> > free
> > > > and open source software: development projects, foundations, meetups,
> > > > hackathons, conference committees, and more. If you’re not sure
> whether
> > > > your organization qualifies, send us an email at supp...@zulip.com.”
> > > >
> > > > zoran
> > > > --
> > > > Sent from mobile
> > > >
> > > > > On 21. Aug 2020, at 11:18, Zoran Regvart 
> wrote:
> > > > >
> > > > > Hi Luca,
> > > > > are you referring to “Funds the Zulip open source project“? I read
> > that
> > > > as “it provides funding to Zulip project”.
> > > > >
> > > > > zoran
> > > > > --
> > > > > Sent from mobile
> > > > >
> > > > >> On 21. Aug 2020, at 10:07, Luca Burgazzoli  >
> > > > wrote:
> > > > >>
> > > > >> ---
> > > > >> Luca Burgazzoli
> > > > >>
> > > > >>
> > > > >>>> On Thu, Aug 20, 2020 at 7:23 PM Zoran Regvart <
> zo...@regvart.com>
> > > > wrote:
> > > > >>>
> > > > >>> Hi Cameleers,
> > > > >>> I also think Gitter is a bit hard to follow, especially when
> there
> > are
> > > > >>> a lot of messages flowing by (reminds me of IRC).
> > > > >>>
> > > > >>> I do wonder how Zulip would be set up, I don't see an OpenSource
> > plan
> > > > >>> on zulipchat.com[1] and I don't think it's good practice for an
> > open
> > > > >>> source community to lose messages. Gitter offers unlimited
> > history[2].
> > > > >>>
> > > > >>>
> > > > >> It looks like that zulip cloud standard is free for open source
> > projects
> > > > >> according to the FAQs https://zulipchat.com/plans or I'm reading
> it
> > > > wrong ?
> > > > >>
> > > > >>
> > > > >>> We could try to ask INFRA to provide a Zulip service Camel/ASF
> > wide.
> > > > >>>
> > > > >>> zoran
> > > > >>>
> > > > >>> [1] https://zulipchat.com/plans/
> > > > >>> [2]
> > > >
> https://gitter.zendesk.com/hc/en-us/articles/202169471-Message-history
> > > > >>>
> > > > >>>> On Thu, Aug 20, 2020 at 1:12 PM Luca Burgazzoli <
> > > > lburgazz...@gmail.com>
> > > > >>>> wrote:
> > > > >>>>
> > > > >>>> Hello,
> > > > >>>>
> > > > >>>> Over the past months I've been trying to be mo

Re: [VOTE] Release Apache Camel Quarkus 1.0.1

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Thu, Aug 27, 2020 at 6:49 AM Andrea Cosentino  wrote:

> +1 (binding)
>
> Thanks Peter.
>
> Il giorno mer 26 ago 2020 alle ore 22:05 Peter Palaga 
> ha scritto:
>
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 1.0.1 - the first patch
> > release in the new 1.0.x branch.
> >
> > Highlights:
> > * Camel 3.4.3
> > * Quarkus 1.7.1.Final
> > * All changes since 1.0.0 (all backported from the master)
> > https://github.com/apache/camel-quarkus/compare/1.0.0...1.0.1
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1242
> >
> >
> > Tag:
> >
> >
> https://gitbox.apache.org/repos/asf?p=camel-quarkus.git;a=commit;h=c324819b5aa0071f3c4ee942949b46eefcf3e2eb
> >
> > Source release package:
> >
> >
> https://repository.apache.org/service/local/repositories/orgapachecamel-1242/content/org/apache/camel/quarkus/camel-quarkus/1.0.1/camel-quarkus-1.0.1-src.zip
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel Quarkus 1.0.1
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Many thanks to all contributors!
> >
> > -- Peter
> >
> >
>

Re: Alternatives to gitter

[Luca Burgazzoli]

So I've created a new Zulip organization for testing purposes here:
https://camel-test.zulipchat.com (I've named it camel-test as there's an
option to import gitter chats but can be done only for new organization)
Anyone should be able to join using github/gitlab/google, by mail or with
an invitation.

I've also had some discussion with the Zulip team as well as other teams
using Zulip and I can confirm that it is possible to request a standard
plan for open source so we can get rid of the message history issue.

---
Luca Burgazzoli


On Fri, Aug 21, 2020 at 11:22 AM Zoran Regvart  wrote:

> Never mind, found the answer in the second link you posted:
>
> https://zulipchat.com/for/open-source/
>
> “Free hosting at zulip.com.
> The hosting is supported by (and is identical to) zulip.com’s commercial
> offerings. This offer extends to any community involved in supporting free
> and open source software: development projects, foundations, meetups,
> hackathons, conference committees, and more. If you’re not sure whether
> your organization qualifies, send us an email at supp...@zulip.com.”
>
> zoran
> --
> Sent from mobile
>
> > On 21. Aug 2020, at 11:18, Zoran Regvart  wrote:
> >
> > Hi Luca,
> > are you referring to “Funds the Zulip open source project“? I read that
> as “it provides funding to Zulip project”.
> >
> > zoran
> > --
> > Sent from mobile
> >
> >> On 21. Aug 2020, at 10:07, Luca Burgazzoli 
> wrote:
> >>
> >> ---
> >> Luca Burgazzoli
> >>
> >>
> >>>> On Thu, Aug 20, 2020 at 7:23 PM Zoran Regvart 
> wrote:
> >>>
> >>> Hi Cameleers,
> >>> I also think Gitter is a bit hard to follow, especially when there are
> >>> a lot of messages flowing by (reminds me of IRC).
> >>>
> >>> I do wonder how Zulip would be set up, I don't see an OpenSource plan
> >>> on zulipchat.com[1] and I don't think it's good practice for an open
> >>> source community to lose messages. Gitter offers unlimited history[2].
> >>>
> >>>
> >> It looks like that zulip cloud standard is free for open source projects
> >> according to the FAQs https://zulipchat.com/plans or I'm reading it
> wrong ?
> >>
> >>
> >>> We could try to ask INFRA to provide a Zulip service Camel/ASF wide.
> >>>
> >>> zoran
> >>>
> >>> [1] https://zulipchat.com/plans/
> >>> [2]
> https://gitter.zendesk.com/hc/en-us/articles/202169471-Message-history
> >>>
> >>>> On Thu, Aug 20, 2020 at 1:12 PM Luca Burgazzoli <
> lburgazz...@gmail.com>
> >>>> wrote:
> >>>>
> >>>> Hello,
> >>>>
> >>>> Over the past months I've been trying to be more active on gitter on
> the
> >>>> various camel projects and  overall the user experience was quite
> >>> terrible
> >>>> for me (in particular when using the mobile client), as example:
> >>>>
> >>>> - threads are not shown properly on the iOS client thus messages are
> >>>> messing up
> >>>> - messages are extremely slow to load and sometime the message you
> sent
> >>>> take quite long to be visible even on your end so you don't actually
> know
> >>>> what it is happening
> >>>> - messages keep being marked as unread even if you did read them
> >>>> - sometimes you need to close/reopen the thread sidebar to see new
> >>> messages
> >>>> for a given thread
> >>>>
> >>>> I don't know if it is only me but because of my frustration with the
> tool
> >>>> I'd like to know if anyone is interested in evaluating some
> alternatives
> >>>> (please note that we DON'T necessarily need to switch to something
> >>>> different).
> >>>>
> >>>> I'd personally would like to suggest to try out Zulip (
> >>>> https://zulipchat.com/) as it allow us to have an independent
> >>> organization (
> >>>> camel.zulipchat.com) and to login with github/gitter/google so you
> can
> >>>> easily join without having to fill gazillion of details but I know
> it's
> >>>> streams and topic way of organizing conversations may not be optimal
> for
> >>>> everyone.
> >>>>
> >>>> If anyone has suggestions, let discuss here.
> >>>>
> >>>>
> >>>> ---
> >>>> Luca Burgazzoli
> >>>
> >>>
> >>>
> >>> --
> >>> Zoran Regvart
> >>>
>

Re: Alternatives to gitter

[Luca Burgazzoli]

There's some information [¹] about what it is supported and what it is
coming, like support for search engine

[1] https://zulipchat.com/for/open-source/

---
Luca Burgazzoli


On Fri, Aug 21, 2020 at 10:47 AM Alex Dettinger 
wrote:

> No strong opinion about which one is the best.
> However, I find it interesting that gitter conversations could be included
> in search engine results (at least google).
> However, I don't know if we would have this with Zulip or Slack.
>
> On Fri, Aug 21, 2020 at 10:11 AM Jean-Baptiste Onofre 
> wrote:
>
> > Maybe it would be great to have a test period of zulip.
> >
> > I never used it, so, I can’t say if it’s good or not.
> >
> > So, maybe experimenting a bit to have feedback would be great.
> >
> > Regards
> > JB
> >
> > > Le 21 août 2020 à 10:07, Luca Burgazzoli  a
> > écrit :
> > >
> > > ---
> > > Luca Burgazzoli
> > >
> > >
> > > On Thu, Aug 20, 2020 at 7:23 PM Zoran Regvart 
> wrote:
> > >
> > >> Hi Cameleers,
> > >> I also think Gitter is a bit hard to follow, especially when there are
> > >> a lot of messages flowing by (reminds me of IRC).
> > >>
> > >> I do wonder how Zulip would be set up, I don't see an OpenSource plan
> > >> on zulipchat.com[1] and I don't think it's good practice for an open
> > >> source community to lose messages. Gitter offers unlimited history[2].
> > >>
> > >>
> > > It looks like that zulip cloud standard is free for open source
> projects
> > > according to the FAQs https://zulipchat.com/plans or I'm reading it
> > wrong ?
> > >
> > >
> > >> We could try to ask INFRA to provide a Zulip service Camel/ASF wide.
> > >>
> > >> zoran
> > >>
> > >> [1] https://zulipchat.com/plans/
> > >> [2]
> > https://gitter.zendesk.com/hc/en-us/articles/202169471-Message-history
> > >>
> > >> On Thu, Aug 20, 2020 at 1:12 PM Luca Burgazzoli <
> lburgazz...@gmail.com>
> > >> wrote:
> > >>>
> > >>> Hello,
> > >>>
> > >>> Over the past months I've been trying to be more active on gitter on
> > the
> > >>> various camel projects and  overall the user experience was quite
> > >> terrible
> > >>> for me (in particular when using the mobile client), as example:
> > >>>
> > >>> - threads are not shown properly on the iOS client thus messages are
> > >>> messing up
> > >>> - messages are extremely slow to load and sometime the message you
> sent
> > >>> take quite long to be visible even on your end so you don't actually
> > know
> > >>> what it is happening
> > >>> - messages keep being marked as unread even if you did read them
> > >>> - sometimes you need to close/reopen the thread sidebar to see new
> > >> messages
> > >>> for a given thread
> > >>>
> > >>> I don't know if it is only me but because of my frustration with the
> > tool
> > >>> I'd like to know if anyone is interested in evaluating some
> > alternatives
> > >>> (please note that we DON'T necessarily need to switch to something
> > >>> different).
> > >>>
> > >>> I'd personally would like to suggest to try out Zulip (
> > >>> https://zulipchat.com/) as it allow us to have an independent
> > >> organization (
> > >>> camel.zulipchat.com) and to login with github/gitter/google so you
> can
> > >>> easily join without having to fill gazillion of details but I know
> it's
> > >>> streams and topic way of organizing conversations may not be optimal
> > for
> > >>> everyone.
> > >>>
> > >>> If anyone has suggestions, let discuss here.
> > >>>
> > >>>
> > >>> ---
> > >>> Luca Burgazzoli
> > >>
> > >>
> > >>
> > >> --
> > >> Zoran Regvart
> > >>
> >
> >
>

Re: Alternatives to gitter

[Luca Burgazzoli]

---
Luca Burgazzoli


On Thu, Aug 20, 2020 at 7:23 PM Zoran Regvart  wrote:

> Hi Cameleers,
> I also think Gitter is a bit hard to follow, especially when there are
> a lot of messages flowing by (reminds me of IRC).
>
> I do wonder how Zulip would be set up, I don't see an OpenSource plan
> on zulipchat.com[1] and I don't think it's good practice for an open
> source community to lose messages. Gitter offers unlimited history[2].
>
>
It looks like that zulip cloud standard is free for open source projects
according to the FAQs https://zulipchat.com/plans or I'm reading it wrong ?


> We could try to ask INFRA to provide a Zulip service Camel/ASF wide.
>
> zoran
>
> [1] https://zulipchat.com/plans/
> [2] https://gitter.zendesk.com/hc/en-us/articles/202169471-Message-history
>
> On Thu, Aug 20, 2020 at 1:12 PM Luca Burgazzoli 
> wrote:
> >
> > Hello,
> >
> > Over the past months I've been trying to be more active on gitter on the
> > various camel projects and  overall the user experience was quite
> terrible
> > for me (in particular when using the mobile client), as example:
> >
> > - threads are not shown properly on the iOS client thus messages are
> > messing up
> > - messages are extremely slow to load and sometime the message you sent
> > take quite long to be visible even on your end so you don't actually know
> > what it is happening
> > - messages keep being marked as unread even if you did read them
> > - sometimes you need to close/reopen the thread sidebar to see new
> messages
> > for a given thread
> >
> > I don't know if it is only me but because of my frustration with the tool
> > I'd like to know if anyone is interested in evaluating some alternatives
> > (please note that we DON'T necessarily need to switch to something
> > different).
> >
> > I'd personally would like to suggest to try out Zulip (
> > https://zulipchat.com/) as it allow us to have an independent
> organization (
> > camel.zulipchat.com) and to login with github/gitter/google so you can
> > easily join without having to fill gazillion of details but I know it's
> > streams and topic way of organizing conversations may not be optimal for
> > everyone.
> >
> > If anyone has suggestions, let discuss here.
> >
> >
> > ---
> > Luca Burgazzoli
>
>
>
> --
> Zoran Regvart
>

Re: Alternatives to gitter

[Luca Burgazzoli]

Yes but you either need to use a Google account or you need to have an @
apache.org mail address or get an invitation, not a huge deal but having
the option to join with github/gitlab is IMHO a good thing.

---
Luca Burgazzoli


On Thu, Aug 20, 2020 at 2:18 PM Jean-Baptiste Onofre 
wrote:

> Hi,
>
> Anyone can join now afair.
>
> Anyway, for sure gitter is not convenient IMHO, the UI is horrible and the
> iOS/Android clients are so so.
>
> We use Slack in bunch of Apache project and it’s good enough to me.
>
> Regards
> JB
>
> > Le 20 août 2020 à 14:14, Luca Burgazzoli  a
> écrit :
> >
> > The main reason not to use Slack - IMHO - is that is not straightforward
> to
> > join using one of the account most of the people already have
> >
> > ---
> > Luca Burgazzoli
> >
> >
> > On Thu, Aug 20, 2020 at 1:36 PM Francois Papon <
> francois.pa...@openobject.fr>
> > wrote:
> >
> >> Hi,
> >>
> >> Why not using the ASF Slack workspace?
> >>
> >> There is an existing Camel channel.
> >>
> >> regards,
> >>
> >> François
> >> fpa...@apache.org
> >>
> >> Le 20/08/2020 à 13:12, Luca Burgazzoli a écrit :
> >>> Hello,
> >>>
> >>> Over the past months I've been trying to be more active on gitter on
> the
> >>> various camel projects and  overall the user experience was quite
> >> terrible
> >>> for me (in particular when using the mobile client), as example:
> >>>
> >>> - threads are not shown properly on the iOS client thus messages are
> >>> messing up
> >>> - messages are extremely slow to load and sometime the message you sent
> >>> take quite long to be visible even on your end so you don't actually
> know
> >>> what it is happening
> >>> - messages keep being marked as unread even if you did read them
> >>> - sometimes you need to close/reopen the thread sidebar to see new
> >> messages
> >>> for a given thread
> >>>
> >>> I don't know if it is only me but because of my frustration with the
> tool
> >>> I'd like to know if anyone is interested in evaluating some
> alternatives
> >>> (please note that we DON'T necessarily need to switch to something
> >>> different).
> >>>
> >>> I'd personally would like to suggest to try out Zulip (
> >>> https://zulipchat.com/) as it allow us to have an independent
> >> organization (
> >>> camel.zulipchat.com) and to login with github/gitter/google so you can
> >>> easily join without having to fill gazillion of details but I know it's
> >>> streams and topic way of organizing conversations may not be optimal
> for
> >>> everyone.
> >>>
> >>> If anyone has suggestions, let discuss here.
> >>>
> >>>
> >>> ---
> >>> Luca Burgazzoli
> >>>
> >>
>
>

Re: Alternatives to gitter

[Luca Burgazzoli]

---
Luca Burgazzoli


On Thu, Aug 20, 2020 at 1:37 PM Omar Al-Safi  wrote:

> Hi Luca,
>
> Yes is true, gitter clients on Android and iOS not the best, also zulip
> looks nice, however my concerns would be the maintenance overhead, we have
> now gitter and mailing list which is enough I think. If we introduce a
> third tool, this could be annoying to keep track of, is just my personal
> opinion on this of course.
>
>
I think that if we introduce another tool, the we need to sunset giotter,
we can keep it open for some time but at certain point, we should have only
one IM


> Also, it would be nice if we can evaluate zulip on a small scale and
> compare it with gitter.
>
> On the chat topic, it would be nice if we can have a `dev` room where we
> can discuss dev topics in relation to Camel (something similar to Debezium
> dev channel on gitter), instead of email/jira as sometimes brainstorming as
> async manner would make more sense.
>

Yeah, it could be much easier with tools like zulip as you can control what
channel/streams to create so we can have everything about camel in a single
place


>
> Regards,
> Omar
>
> On Thu, Aug 20, 2020 at 1:12 PM Luca Burgazzoli 
> wrote:
>
> > Hello,
> >
> > Over the past months I've been trying to be more active on gitter on the
> > various camel projects and  overall the user experience was quite
> terrible
> > for me (in particular when using the mobile client), as example:
> >
> > - threads are not shown properly on the iOS client thus messages are
> > messing up
> > - messages are extremely slow to load and sometime the message you sent
> > take quite long to be visible even on your end so you don't actually know
> > what it is happening
> > - messages keep being marked as unread even if you did read them
> > - sometimes you need to close/reopen the thread sidebar to see new
> messages
> > for a given thread
> >
> > I don't know if it is only me but because of my frustration with the tool
> > I'd like to know if anyone is interested in evaluating some alternatives
> > (please note that we DON'T necessarily need to switch to something
> > different).
> >
> > I'd personally would like to suggest to try out Zulip (
> > https://zulipchat.com/) as it allow us to have an independent
> > organization (
> > camel.zulipchat.com) and to login with github/gitter/google so you can
> > easily join without having to fill gazillion of details but I know it's
> > streams and topic way of organizing conversations may not be optimal for
> > everyone.
> >
> > If anyone has suggestions, let discuss here.
> >
> >
> > ---
> > Luca Burgazzoli
> >
>

Re: Alternatives to gitter

[Luca Burgazzoli]

The main reason not to use Slack - IMHO - is that is not straightforward to
join using one of the account most of the people already have

---
Luca Burgazzoli


On Thu, Aug 20, 2020 at 1:36 PM Francois Papon 
wrote:

> Hi,
>
> Why not using the ASF Slack workspace?
>
> There is an existing Camel channel.
>
> regards,
>
> François
> fpa...@apache.org
>
> Le 20/08/2020 à 13:12, Luca Burgazzoli a écrit :
> > Hello,
> >
> > Over the past months I've been trying to be more active on gitter on the
> > various camel projects and  overall the user experience was quite
> terrible
> > for me (in particular when using the mobile client), as example:
> >
> > - threads are not shown properly on the iOS client thus messages are
> > messing up
> > - messages are extremely slow to load and sometime the message you sent
> > take quite long to be visible even on your end so you don't actually know
> > what it is happening
> > - messages keep being marked as unread even if you did read them
> > - sometimes you need to close/reopen the thread sidebar to see new
> messages
> > for a given thread
> >
> > I don't know if it is only me but because of my frustration with the tool
> > I'd like to know if anyone is interested in evaluating some alternatives
> > (please note that we DON'T necessarily need to switch to something
> > different).
> >
> > I'd personally would like to suggest to try out Zulip (
> > https://zulipchat.com/) as it allow us to have an independent
> organization (
> > camel.zulipchat.com) and to login with github/gitter/google so you can
> > easily join without having to fill gazillion of details but I know it's
> > streams and topic way of organizing conversations may not be optimal for
> > everyone.
> >
> > If anyone has suggestions, let discuss here.
> >
> >
> > ---
> > Luca Burgazzoli
> >
>

Alternatives to gitter

[Luca Burgazzoli]

Hello,

Over the past months I've been trying to be more active on gitter on the
various camel projects and  overall the user experience was quite terrible
for me (in particular when using the mobile client), as example:

- threads are not shown properly on the iOS client thus messages are
messing up
- messages are extremely slow to load and sometime the message you sent
take quite long to be visible even on your end so you don't actually know
what it is happening
- messages keep being marked as unread even if you did read them
- sometimes you need to close/reopen the thread sidebar to see new messages
for a given thread

I don't know if it is only me but because of my frustration with the tool
I'd like to know if anyone is interested in evaluating some alternatives
(please note that we DON'T necessarily need to switch to something
different).

I'd personally would like to suggest to try out Zulip (
https://zulipchat.com/) as it allow us to have an independent organization (
camel.zulipchat.com) and to login with github/gitter/google so you can
easily join without having to fill gazillion of details but I know it's
streams and topic way of organizing conversations may not be optimal for
everyone.

If anyone has suggestions, let discuss here.


---
Luca Burgazzoli

Re: [VOTE] Release Apache Camel 3.4.3 (LTS)

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Wed, Aug 12, 2020 at 2:08 PM Omar Al-Safi  wrote:

> +1 (binding)
>
> Thank you
>
> On Wed, Aug 12, 2020 at 2:06 PM Andrea Cosentino 
> wrote:
>
> > +1 (binding)
> >
> > Thanks Gregor!
> >
> > Il mer 12 ago 2020, 09:56 Gregor Zurowski  ha
> > scritto:
> >
> > > Hi Everyone:
> > >
> > > This is a vote to release Apache Camel 3.4.3, a new patch release for
> > > the 3.4.x LTS branch with 33 improvements and fixes.
> > >
> > > Release notes:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12348603=12311211
> > >
> > > == Apache Camel 3.4.3 ==
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1239/
> > >
> > > Tarballs:
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1239/org/apache/camel/apache-camel/3.4.3/
> > >
> > > Tag:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.4.3
> > >
> > > == Apache Camel Spring Boot 3.4.3 ==
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1240/
> > >
> > > Tag:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.4.3
> > >
> > > == Apache Camel Karaf 3.4.3 ==
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1241/
> > >
> > > Tag:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.4.3
> > >
> > > Please test this release candidate and cast your vote.
> > > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > > Karaf 3.4.3
> > > [ ] -1 Veto the release (provide specific comments)
> > >
> > > The vote is open for at least 72 hours.
> > >
> > > Thanks,
> > > Gregor
> > >
> >
>

Re: [VOTE] Release Apache Camel Quarkus 1.0.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Tue, Aug 11, 2020 at 4:30 PM Jean-Baptiste Onofre 
wrote:

> +1 (binding)
>
> Regards
> JB
>
> > Le 11 août 2020 à 15:07, Alex Dettinger  a écrit
> :
> >
> > +1 (binding)
> >
> > No show stopper on my side. Built from source package, run some
> > itests/examples, built an app on top of quarkus-bom, scratched
> > dev/jvm/native/properties/healthcheck...
> > Alex
> >
> > On Mon, Aug 10, 2020 at 1:42 PM Peter Palaga  wrote:
> >
> >> https://repository.apache.org/content/repositories/orgapachecamel-1238/
> >> should work now. I forgot to close it. Thanks Luca for noting it!
> >>
> >> Sorry for the confusion
> >>
> >> -- P
> >>
> >> On 10/08/2020 13:10, Peter Palaga wrote:
> >>> Hi,
> >>>
> >>> This is a vote to release Apache Camel Quarkus 1.0.0.
> >>>
> >>> Highlights:
> >>> * Based on LTS Camel 3.4.x
> >>> * Quarkus 1.7.0.Final
> >>> * Fixed issues:
> >>> https://github.com/apache/camel-quarkus/milestone/1?closed=1
> >>>
> >>> Staging repository:
> >>> https://repository.apache.org/content/repositories/orgapachecamel-1238
> >>>
> >>>
> >>> Tag:
> >>>
> >>
> https://gitbox.apache.org/repos/asf?p=camel-quarkus.git;a=tag;h=c8be84fe0208ae87be32feeaa444c0caa4d19a38
> >>>
> >>>
> >>> Source release package:
> >>>
> >>
> https://repository.apache.org/service/local/repositories/orgapachecamel-1238/content/org/apache/camel/quarkus/camel-quarkus/1.0.0/camel-quarkus-1.0.0-src.zip
> >>>
> >>>
> >>> Please test this release candidate and cast your vote.
> >>>
> >>> [ ] +1 Release the binary as Apache Camel Quarkus 1.0.0
> >>> [ ] -1 Veto the release (provide specific comments)
> >>>
> >>> The vote is open for at least 72 hours.
> >>>
> >>> Many thanks to all contributors!
> >>>
> >>> -- Peter
> >>
> >>
>
>

Re: [VOTE] Release Apache Camel K 1.1.0 and Runtime 1.4.1

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Tue, Jul 21, 2020 at 3:33 PM Nicola Ferraro  wrote:

> Hello all:
>
> This is a vote to release Apache Camel K 1.1.0 and Camel K Runtime 1.4.1.
>
> This is intended to be a stable release before major changes are added.
> More details on the release notes:
> https://github.com/apache/camel-k/issues/1618#issuecomment-661859438
>
> Runtime staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1235
> Runtime Tag:
>
> https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-parent-1.4.1
>
> Camel K staging repository:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/1.1.0/
> Camel K Tag:
>
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/v1.1.0
>
> Staging container image repository:
> https://hub.docker.com/r/camelk/camel-k
> /tags
>
> It's possible to install all staging artifacts with a single command:
> kamel install --operator-image=camelk/camel-k:1.1.0 --maven-repository=
> https://repository.apache.org/content/repositories/orgapachecamel-1235
>  --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel K 1.1.0 and Apache Camel K
> Runtime
> 1.4.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Nicola Ferraro
>

Re: [VOTE] Release Apache Camel 3.4.2 with Spring Boot and Karaf Support Projects

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Jul 20, 2020 at 10:00 AM Claus Ibsen  wrote:

> +1 (binding)
>
> On Sun, Jul 19, 2020 at 9:14 PM Gregor Zurowski
>  wrote:
> >
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 3.4.2 (with Apache Camel Spring
> > Boot and Apache Camel Karaf), the second patch release for the 3.4 LTS
> > branch with 5 improvements and fixes. The main reason we are releasing
> > this version is that we compiled 3.4.1 with Java 11 which leads to
> > issues as described in [1]. Although we are already working on a fix
> > for this problem (see ticket [2]), we found that it would be safer to
> > quickly push out a release compiled with Java 8 so our users are not
> > affected by this. We plan to continue compiling with Java 8 until we
> > eventually make Java 11 the base version for Camel.
> >
> > Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12348562=12311220
> >
> > == Apache Camel 3.4.2 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1232/
> >
> > Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1232/org/apache/camel/apache-camel/3.4.2/
> >
> > Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.4.2
> >
> > == Apache Camel Spring Boot 3.4.2 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1233/
> >
> > Tag:
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.4.2
> >
> > == Apache Camel Karaf 3.4.2 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1234/
> >
> > Tag:
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.4.2
> >
> > Please test this release candidate and cast your vote.
> > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > Karaf 3.4.2
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
> >
> > [1] https://github.com/eclipse/jetty.project/issues/3244
> > [2] https://issues.apache.org/jira/browse/CAMEL-15309
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: [VOTE] Release Apache Camel 3.4.1 with Spring Boot and Karaf Support Projects

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Tue, Jul 14, 2020 at 11:20 AM Djordje Bajić 
wrote:

> +1
>
> On Tue, Jul 14, 2020 at 11:02 AM Zoran Regvart  wrote:
>
> > +1 (binding)
> >
> > Thanks Gregor!
> > --
> > Sent from mobile
> >
> > > On 13. Jul 2020, at 12:06, Gregor Zurowski 
> > wrote:
> > >
> > > Hi Everyone:
> > >
> > > This is a vote to release Apache Camel 3.4.1 (with Apache Camel Spring
> > > Boot and Apache Camel Karaf), the first patch release for the 3.4 LTS
> > > branch with 20 improvements and fixes.
> > >
> > > Release notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12348393=12311220
> > >
> > > == Apache Camel 3.4.1 ==
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1225/
> > >
> > > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1225/org/apache/camel/apache-camel/3.4.1/
> > >
> > > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.4.1
> > >
> > > == Apache Camel Spring Boot 3.4.1 ==
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1226/
> > >
> > > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.4.1
> > >
> > > == Apache Camel Karaf 3.4.1 ==
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1227/
> > >
> > > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.4.1
> > >
> > > Please test this release candidate and cast your vote.
> > > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > > Karaf 3.4.1
> > > [ ] -1 Veto the release (provide specific comments)
> > >
> > > The vote is open for at least 72 hours.
> > >
> > > Thanks,
> > > Gregor
> >
>
>
> --
> - Đorđe Bajić
>

Re: [VOTE] Release Apache Camel Quarkus 1.0.0-CR3

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Jul 6, 2020 at 1:03 PM Willem Jiang  wrote:

> Yeah, I'm fine with that now.  Here is my +1.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Jul 6, 2020 at 2:06 PM James Netherton 
> wrote:
> >
> > I merged: https://github.com/apache/camel-quarkus/pull/1458.
> >
> > Willem - you're now +1 for the release, right?
> >
> >
> > On Mon, 6 Jul 2020 at 03:11, Willem Jiang 
> wrote:
> > >
> > > Done,  I just filled an issue[1] to track it and sent a PR[2] to fix
> it.
> > >
> > > [1]https://github.com/apache/camel-quarkus/pull/1455
> > > [2]https://github.com/apache/camel-quarkus/pull/1458
> > >
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Sat, Jul 4, 2020 at 2:38 PM Claus Ibsen 
> wrote:
> > > >
> > > > On Sat, Jul 4, 2020 at 3:55 AM Willem Jiang 
> wrote:
> > > > >
> > > > > -1.
> > > > > I just checked the source release package[1], there are some binary
> > > > > files in the docs/node directory.
> > > > > I checked the git repo, there is no docs/node directory.
> > > > > As we are not supposed to ship the binary files in the source kit,
> so
> > > > > I vote -1 for this release.
> > > > >
> > > >
> > > > I checked the RC2 and it was also a binary file there.
> > > > Can you create a JIRA ticket about this so it can be fixed in RC4.
> > > >
> > > > Lets this release go ahead - the community wans to get hands on this
> > > > with the Camel 3.4 upgrade - and they frankly dont care about a node
> > > > binary file.
> > > >
> > > >
> > > >
> > > > > [1]
> https://repository.apache.org/service/local/repositories/orgapachecamel-1224/content/org/apache/camel/quarkus/camel-quarkus/1.0.0-CR3/camel-quarkus-1.0.0-CR3-src.zip
> > > > >
> > > > > Willem Jiang
> > > > >
> > > > > Twitter: willemjiang
> > > > > Weibo: 姜宁willem
> > > > >
> > > > > On Fri, Jul 3, 2020 at 5:41 PM Peter Palaga 
> wrote:
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > This is a vote to release Apache Camel Quarkus 1.0.0-CR3.
> > > > > >
> > > > > > Highlights (same as 1.0.0-CR1):
> > > > > > * Camel 3.4.0
> > > > > > * Quarkus 1.6.0.Final
> > > > > > * Fixed issues:
> https://github.com/apache/camel-quarkus/milestone/3?closed=1
> > > > > >
> > > > > > Staging repository:
> > > > > >
> https://repository.apache.org/content/repositories/orgapachecamel-1224
> > > > > >
> > > > > >
> > > > > > Tag:
> > > > > >
> https://gitbox.apache.org/repos/asf?p=camel-quarkus.git;a=tag;h=e10cfef86e5c3c6670f87a3c1d877f7ebc54e615
> > > > > >
> > > > > > Source release package:
> > > > > >
> https://repository.apache.org/service/local/repositories/orgapachecamel-1224/content/org/apache/camel/quarkus/camel-quarkus/1.0.0-CR3/camel-quarkus-1.0.0-CR3-src.zip
> > > > > >
> > > > > > Please test this release candidate and cast your vote.
> > > > > >
> > > > > > [ ] +1 Release the binary as Apache Camel Quarkus 1.0.0-CR3
> > > > > > [ ] -1 Veto the release (provide specific comments)
> > > > > >
> > > > > > The vote is open for at least 72 hours.
> > > > > >
> > > > > > Many thanks to all contributors!
> > > > > >
> > > > > > -- Peter
> > > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Claus Ibsen
> > > > -
> > > > http://davsclaus.com @davsclaus
> > > > Camel in Action 2: https://www.manning.com/ibsen2
>

Re: [HEADS UP] - Java 8 to be dropped

[Luca Burgazzoli]

I'd say that we'll have the same discussion for Java 14, hopefully not for
keeping Java 8 but maybe for Java 11 so I think what we need to define is
the policy, rather than the specific version.

---
Luca Burgazzoli


On Tue, Jun 30, 2020 at 4:56 PM Guillaume Nodet  wrote:

> Oh, I wasn't even considering it if it can't be done in a single automated
> maven run.
> I haven't checked with latest maven plugins, but I was more thinking about
> the cost of managing multiple versions of the same source file and how IDE
> can support those.
> See https://www.baeldung.com/maven-multi-release-jars
> I think it can be done for specific spots where it makes sense.
>
> Here's a short list of JDK language enhancements:
> JDK 9-10-11:
>   * .of()
>   * more functions in the stream api
>   * private interface methods
>   * http/2 client support
>   * local-variable type inference in variables and lambda parameters
>   * new String methods : isBlank(), lines(), repeat(int), unicode aware
> strip(), stripLeading() and stripTrailing()
>   * new File methods: writeString(), readString() and isSameFile()
> JDK 12-13-14:
>   * switch expressions
>   * teeing in the stream api
>   * new String methods: indent(), transform(), formatted(), striIndent(),
> translateEscapes()
>   * new Files.mismatch() method
>
> I'd be more inclined to wait a bit and jump straight to JDK 14 to be able
> to leverage the switch expressions.  For new methods on String / File, we
> could prepare the code by adding helper methods that would simply call the
> JDK ones by leveraging multi-release jars if it can prove useful.
>
> Another thought would be to leverage some tool like jabel (
> https://github.com/bsideup/jabel) to be able to leverage pure syntactic
> sugar improvements, but i've tried to get rid of annotation processors the
> last months, so not sure that's a good idea.
>
> Le mar. 30 juin 2020 à 14:20, Andrea Cosentino  a
> écrit :
>
> > I don't know if it's feasible, we are already demanding a lot of work to
> > the release manager and I guess going through the multi release jar
> > approach will be much more troublesome.
> >
> > Il giorno mar 30 giu 2020 alle ore 14:14 Guillaume Nodet <
> > gno...@apache.org>
> > ha scritto:
> >
> > > We could try using the multi-release jar feature in order to leverage
> new
> > > JDK 11 or JDK 14 features without completely dropping JDK 8, but that's
> > > definitely more work.  I haven't seen many projects using it yet, so
> not
> > > sure how that's manageable from a development perspective.
> > >
> > > Le mar. 30 juin 2020 à 13:50, Luca Burgazzoli 
> a
> > > écrit :
> > >
> > > > I think that unless someone "big" in the OSS makes a move, most
> > libraries
> > > > will stay with Java 8 till they are forced so I guess someone should
> be
> > > > brave and make the move.
> > > >
> > > > ---
> > > > Luca Burgazzoli
> > > >
> > > >
> > > > On Tue, Jun 30, 2020 at 12:57 PM Peter Palaga 
> > > wrote:
> > > >
> > > > > On 30/06/2020 09:29, Jean-Baptiste Onofre wrote:
> > > > > > Agree, I think we should be very careful about communication.
> > > > > >
> > > > > > It’s the same about EOL branch/release. Actually EOL doesn’t
> really
> > > > > exist at Apache: anyone can fix/change an old branch and cut a
> > release
> > > on
> > > > > it.
> > > > > > So, I fully understand the purpose, but I think we should be more
> > > > > "flexible" and communicate early enough to our users.
> > > > > >
> > > > > > Regards
> > > > > > JB
> > > > > >
> > > > > >> Le 29 juin 2020 à 22:23, Guillaume Nodet  a
> > > écrit
> > > > :
> > > > > >>
> > > > > >> Note that we changed a bunch of lambda expressions back to
> > anonymous
> > > > > >> classes a few months ago, so trying to get to the latest is not
> > > always
> > > > > the
> > > > > >> best choice.
> > > > > >> I'm not sure we need to drop Java 8 now.  We can defer that
> > decision
> > > > > until
> > > > > >> we have more incentive I think.,
> > > > > >>
> > > > > >> Le lun. 29 juin 2020 à 18:01, Peter Palaga 
> a
> > > > > écrit :
> > > > > >>
> >

Re: [HEADS UP] - Java 8 to be dropped

[Luca Burgazzoli]

I think that unless someone "big" in the OSS makes a move, most libraries
will stay with Java 8 till they are forced so I guess someone should be
brave and make the move.

---
Luca Burgazzoli


On Tue, Jun 30, 2020 at 12:57 PM Peter Palaga  wrote:

> On 30/06/2020 09:29, Jean-Baptiste Onofre wrote:
> > Agree, I think we should be very careful about communication.
> >
> > It’s the same about EOL branch/release. Actually EOL doesn’t really
> exist at Apache: anyone can fix/change an old branch and cut a release on
> it.
> > So, I fully understand the purpose, but I think we should be more
> "flexible" and communicate early enough to our users.
> >
> > Regards
> > JB
> >
> >> Le 29 juin 2020 à 22:23, Guillaume Nodet  a écrit :
> >>
> >> Note that we changed a bunch of lambda expressions back to anonymous
> >> classes a few months ago, so trying to get to the latest is not always
> the
> >> best choice.
> >> I'm not sure we need to drop Java 8 now.  We can defer that decision
> until
> >> we have more incentive I think.,
> >>
> >> Le lun. 29 juin 2020 à 18:01, Peter Palaga  a
> écrit :
> >>
> >>> On 29/06/2020 11:59, Peter Palaga wrote:
> >>>> On 29/06/2020 07:29, Claus Ibsen wrote:
> >>>>> Hi
> >>>>>
> >>>>> On Sun, Jun 28, 2020 at 4:28 PM Peter Palaga 
> >>> wrote:
> >>>>>>
> >>>>>> Hi Claus,
> >>>>>>
> >>>>>> we have announced a similar move for Camel Quarkus some time ago. We
> >>> did
> >>>>>> that based on a similar Quarkus announcement [1]. But when I was
> about
> >>>>>> to perform the necessary changes, it turned out that Quarkus got
> some
> >>>>>> pushback from the users and thus they abandoned the plan without
> >>> letting
> >>>>>> us know - see [2]. As a result, Camel Quarkus also had to revisit
> the
> >>>>>> plan. We have decided to make Java 11 our main build and testing
> JDK,
> >>>>>> but kept both source and target compatibility at Java 8.
> >>>>>>
> >>>>>> Requiring Java 11+ API on the Camel side would put Camel Quarkus in
> a
> >>>>>> bit uncomfortable position: unlike all other extensions offered via
> >>>>>> code.quarkus.io, our extensions would not work on Java 8 in JVM
> mode.
> >>>>>>
> >>>>>> We (Camel community) should figure out how to proceed.
> >>>>>>
> >>>>>
> >>>>> The drop of Java 8 is planned for next LTS (Camel 3.7) which is by
> end
> >>>>> of this year.
> >>>>> So there is still 6 months to go. In that time Quarkus may get to a
> >>>>> point where they have dropped Java 8 as well.
> >>>>>
> >>>>> But for Camel 3.5 we can surely wait to drop Java 8 so it does not
> >>>>> happen soon on the Camel side.
> >>>>>
> >>>>> Would ou you go ask the Quarkus team what new timeframe they have for
> >>>>> dropping Java 8?
> >>>>
> >>>> Asked https://groups.google.com/forum/#!topic/quarkus-dev/7SZAM2BMb9c
> >>>
> >>> They asked back, what are our motivations for removing Java 8. I can
> say
> >>> for myself that it is mainly a simplification of our testing matrix.
> Are
> >>> there any other reasons?
>
> Are there any other benefits of dropping Java 8?
>
> -- P
>
> >>> Besides they noted that Azure Functions still only supports Java 8.
> >>>
> >>> -- P
> >>>
> >>>>
> >>>>>
> >>>>>> [1]
> >>>>>>
> https://quarkus.io/blog/quarkus-1-4-final-released/#java-8-deprecated
> >>>>>> [2]
> >>> https://groups.google.com/d/msg/quarkus-dev/yzEjmYCFbwY/oW64kts3AQAJ
> >>>>>>
> >>>>>> Thanks,
> >>>>>>
> >>>>>> -- Peter
> >>>>>>
> >>>>>> On 26/06/2020 10:23, Claus Ibsen wrote:
> >>>>>>> Hi
> >>>>>>>
> >>>>>>> Just a heads up that from Camel 3.5 onwards we will drop Java 8
> >>>>>>> support.
> >>>>>>>
> >>>>>>> So this means that minimum Java version is now Java 11.
> >>>>>>> We are also working on adding support for Java 14, but it may take
> a
> >>>>>>> few releases, but its planned for the next LTS 3.7 release to have
> >>>>>>> both Java 11 and 14 as supported.
> >>>>>>>
> >>>>>>> Camel 3.4.x is the LTS release that supports both Java 8 and 11,
> and
> >>>>>>> its supported for 1-year (june 2022).
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>
> >> --
> >> 
> >> Guillaume Nodet
> >
>
>

Re: [HEADS UP] - Java 8 to be dropped

[Luca Burgazzoli]

I don't think that migrating to a new version also means that we need to
embrace every new feature automatically but that we can use them when it
makes sense but staying with an older version means that we can't use them
in any case.

---
Luca Burgazzoli


On Mon, Jun 29, 2020 at 10:23 PM Guillaume Nodet  wrote:

> Note that we changed a bunch of lambda expressions back to anonymous
> classes a few months ago, so trying to get to the latest is not always the
> best choice.
> I'm not sure we need to drop Java 8 now.  We can defer that decision until
> we have more incentive I think.,
>
> Le lun. 29 juin 2020 à 18:01, Peter Palaga  a écrit :
>
> > On 29/06/2020 11:59, Peter Palaga wrote:
> > > On 29/06/2020 07:29, Claus Ibsen wrote:
> > >> Hi
> > >>
> > >> On Sun, Jun 28, 2020 at 4:28 PM Peter Palaga 
> > wrote:
> > >>>
> > >>> Hi Claus,
> > >>>
> > >>> we have announced a similar move for Camel Quarkus some time ago. We
> > did
> > >>> that based on a similar Quarkus announcement [1]. But when I was
> about
> > >>> to perform the necessary changes, it turned out that Quarkus got some
> > >>> pushback from the users and thus they abandoned the plan without
> > letting
> > >>> us know - see [2]. As a result, Camel Quarkus also had to revisit the
> > >>> plan. We have decided to make Java 11 our main build and testing JDK,
> > >>> but kept both source and target compatibility at Java 8.
> > >>>
> > >>> Requiring Java 11+ API on the Camel side would put Camel Quarkus in a
> > >>> bit uncomfortable position: unlike all other extensions offered via
> > >>> code.quarkus.io, our extensions would not work on Java 8 in JVM
> mode.
> > >>>
> > >>> We (Camel community) should figure out how to proceed.
> > >>>
> > >>
> > >> The drop of Java 8 is planned for next LTS (Camel 3.7) which is by end
> > >> of this year.
> > >> So there is still 6 months to go. In that time Quarkus may get to a
> > >> point where they have dropped Java 8 as well.
> > >>
> > >> But for Camel 3.5 we can surely wait to drop Java 8 so it does not
> > >> happen soon on the Camel side.
> > >>
> > >> Would ou you go ask the Quarkus team what new timeframe they have for
> > >> dropping Java 8?
> > >
> > > Asked https://groups.google.com/forum/#!topic/quarkus-dev/7SZAM2BMb9c
> >
> > They asked back, what are our motivations for removing Java 8. I can say
> > for myself that it is mainly a simplification of our testing matrix. Are
> > there any other reasons?
> >
> > Besides they noted that Azure Functions still only supports Java 8.
> >
> > -- P
> >
> > >
> > >>
> > >>> [1]
> > >>>
> https://quarkus.io/blog/quarkus-1-4-final-released/#java-8-deprecated
> > >>> [2]
> > https://groups.google.com/d/msg/quarkus-dev/yzEjmYCFbwY/oW64kts3AQAJ
> > >>>
> > >>> Thanks,
> > >>>
> > >>> -- Peter
> > >>>
> > >>> On 26/06/2020 10:23, Claus Ibsen wrote:
> > >>>> Hi
> > >>>>
> > >>>> Just a heads up that from Camel 3.5 onwards we will drop Java 8
> > >>>> support.
> > >>>>
> > >>>> So this means that minimum Java version is now Java 11.
> > >>>> We are also working on adding support for Java 14, but it may take a
> > >>>> few releases, but its planned for the next LTS 3.7 release to have
> > >>>> both Java 11 and 14 as supported.
> > >>>>
> > >>>> Camel 3.4.x is the LTS release that supports both Java 8 and 11, and
> > >>>> its supported for 1-year (june 2022).
> > >>>>
> > >>>>
> > >>>>
> > >>>
> > >>
> > >>
> > >
> >
> >
>
> --
> 
> Guillaume Nodet
>

[HEADS UP] - Kamelets

[Luca Burgazzoli]

Hi,

Over the past months we have been discussing the concept of Kameletes which
in essence is a way to describe a reusable route people can leverage to
provide ready to use functionalities.

It is not the first time a similar concept arises in the Camel community,
think about the RouteBox component and the work around the connectors that
has been done in the past and even if they were interesting concepts they
did not take off for some reasons.

With the introduction of the camel-k subproject, the landscape of
integration with Camel has changed, and we believe we need to bring the
idea of reusable routes to the Cloud Native ages hence we started hacking
on the Kamelets concept under the camel-k umbrella.

To track the work on that area, I've created the following projects:

- https://github.com/apache/camel-k/projects/18
- https://github.com/apache/camel-k-runtime/projects/1

Any feedback would be really appreciated.

---
Luca Burgazzoli

Re: [VOTE] Release Apache Camel K 1.0.1

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Thu, Jun 25, 2020 at 5:01 PM Nicola Ferraro  wrote:

> Hello all:
>
> This is a vote to release Apache Camel K 1.0.1.
>
> This is a maintenance release that addresses some of the issues that have
> been found on the 1.0.0 release. You can see more details in the release
> notes: https://github.com/apache/camel-k/issues/1565#issue-645491033
>
> Camel K staging repository: https://dist.apache.org/repos/dist/dev/camel/
> camel-k/1.0.1/
> <https://dist.apache.org/repos/dist/dev/camel/camel-k/1.0.1/>
> Camel K Tag:
>
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/1.0.1
>
> Staging container image repository:
> https://hub.docker.com/r/camelk/camel-k
> /tags
>
> It's possible to install all staging artifacts with a single command:
> kamel install --operator-image=camelk/camel-k:1.0.1 --olm=false
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel K 1.0.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Nicola Ferraro
>

Re: [VOTE] Release Apache Camel-kafka-connector 0.3.0

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Wed, Jun 17, 2020 at 9:16 PM Zoran Regvart  wrote:

> +1 (binding)
>
> Thanks Andrea for cutting the release :)
>
> zoran
>
> On Wed, Jun 17, 2020 at 2:04 PM Andrea  wrote:
> >
> > Hello all,
> >
> > This is a vote to release Apache Camel-kafka-connector 0.3.0
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1223
> >
> > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-kafka-connector.git;a=tag;h=refs/tags/camel-kafka-connector-0.3.0
> >
> > the main focus of this release has been in stabilizing and polishing the
> integration tests along with updating to camel-3.3.0.
> >
> > Please test this release candidate and cast your vote.
> > [ ] +1 Release the binary as  Apache Camel-kafka-connector 0.3.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 48 hours.
> >
> > Thanks,
> > Andrea.
>
>
>
> --
> Zoran Regvart
>

Re: [VOTE] Release Apache Camel 3.4.0 with Spring Boot and Karaf Support Projects

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Tue, Jun 16, 2020 at 7:10 AM Onder SEZGIN  wrote:

> +1
>
> On Mon, 15 Jun 2020, 23:13 Federico Valeri,  wrote:
>
> > +1
> >
> > On Mon, Jun 15, 2020, 2:38 PM Michael Joyner 
> > wrote:
> >
> > > +1
> > >
> > > On Mon, Jun 15, 2020 at 4:53 AM Jean-Baptiste Onofre 
> > > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > > Le 15 juin 2020 à 09:14, Gregor Zurowski  >
> > a
> > > > écrit :
> > > > >
> > > > > Hi Everyone:
> > > > >
> > > > > This is a vote to release Apache Camel 3.4.0 (with Apache Camel
> > Spring
> > > > > Boot and Apache Camel Karaf), a new minor release with 118
> > > > > improvements and fixes.
> > > > >
> > > > > Release notes:
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12348216=12311220
> > > > >
> > > > > == Apache Camel 3.4.0 ==
> > > > >
> > > > > Staging repository:
> > > > >
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1220/
> > > > >
> > > > > Tarballs:
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1220/org/apache/camel/apache-camel/3.4.0/
> > > > >
> > > > > Tag:
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.4.0
> > > > >
> > > > > == Apache Camel Spring Boot 3.4.0 ==
> > > > >
> > > > > Staging repository:
> > > > >
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1221/
> > > > >
> > > > > Tag:
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.4.0
> > > > >
> > > > > == Apache Camel Karaf 3.4.0 ==
> > > > >
> > > > > Staging repository:
> > > > >
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1222/
> > > > >
> > > > > Tag:
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.4.0
> > > > >
> > > > > Please test this release candidate and cast your vote.
> > > > > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and
> > Camel
> > > > > Karaf 3.4.0
> > > > > [ ] -1 Veto the release (provide specific comments)
> > > > >
> > > > > The vote is open for at least 72 hours.
> > > > >
> > > > > Thanks,
> > > > > Gregor
> > > >
> > > >
> > >
> > > --
> > > --
> > > Michael Joyner
> > > Solutions Architect
> > > SugarCRM
> > >
> > > mobile: (206)-288-3937
> > > email: michaelwjoy...@gmail.com
> > > <https://facebook.com/michaelwjoyner>..
> > >
> >
>

Re: camel-k: switch to Quarkus as default framework for integrations

[Luca Burgazzoli]

Opened the following two issues:

- https://github.com/apache/camel-k/issues/1513
- https://github.com/apache/camel-k-runtime/issues/359

---
Luca Burgazzoli


On Mon, Jun 8, 2020 at 10:15 AM Otavio Rodolfo Piske 
wrote:

> I think this is a good idea.
>
> +1
>
> On Sat, Jun 6, 2020 at 7:57 AM Claus Ibsen  wrote:
>
> > +1
> >
> > On Fri, Jun 5, 2020 at 1:45 PM Luca Burgazzoli 
> > wrote:
> > >
> > > Hello everyone,
> > >
> > > When we started working on camel-k, we haven't found any
> > runtime/framework
> > > that could cope with the type of workloads we had in mind for camel-k
> so
> > we
> > > ended up rolling our own framework but later on the Quarkus project has
> > > started and that has changed a little the landscape as the Quarkus goal
> > is
> > > to support the very same cloud native workload swe want to support so
> we
> > > have added support for Quarkus in camel-k.
> > >
> > > So as today we have two runtimes on which integrations can run:
> > > - our in-house one based on camel-main
> > > - a Quarkus based one that leverages the camel-quarkus project
> > >
> > > Here I'm proposing that after camel-k 1.0.0 we'll drop support for the
> > > in-house framework and focus our effort on making Quarkus the
> foundation
> > > for camel-k runtimes (the integrations) as:
> > >
> > > 1. Maintaining the two runtimes is becoming a challenge as a lot of
> > > features we want are already provided by Quarkus and to make the
> runtimes
> > > on par we need to develop the same set of features on our in-house
> > > framework (think about health checks, integration with tracing and
> > > monitoring, security, etc.). For the end-users it is also confusing as
> > the
> > > two runtimes have a different set of configuration options so even if
> > > there's no difference between how routes are written using one or the
> > other
> > > runtime is not completely transparent.
> > >
> > > 2. Quarkus offers faster startup and reduced memory footprint by moving
> > > some of the initialization at build time which copes perfectly with our
> > > camel-k design as we can make optimized images once and re-use them
> for a
> > > number of integrations.
> > >
> > > 3. Quarkus and the Camel Quarkus subproject can help us to leverage
> > native
> > > compilation when possible which fits perfectly with the serverless
> > workload
> > > we want camel-k to target.
> > >
> > >
> > > What do you think ?
> > >
> > >
> > >
> > >
> > >
> > >
> > > ---
> > > Luca Burgazzoli
> >
> >
> >
> > --
> > Claus Ibsen
> > -
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
>
> --
> Otavio R. Piske
> http://orpiske.net
>

Re: [VOTE] Release Apache Camel K 1.0.0 and Runtime 1.3.0

[Luca Burgazzoli]

+1 (binding)


On Mon, 8 Jun 2020 at 07:54, Andrea Cosentino  wrote:

> +1 (binding)
>
> Thanks!
>
> Il giorno ven 5 giu 2020 alle ore 22:16 Nicola Ferraro <
> nferr...@apache.org>
> ha scritto:
>
> > Hello all:
> >
> > Finally, we're here. This is a combined vote to release Apache Camel K
> > 1.0.0 and
> > Apache Camel K Runtime 1.3.0.
> >
> > Camel K is going GA with this 1.0.0 release, which contains a great
> number
> > of improvements, as you can see in the release notes:
> > https://github.com/apache/camel-k/issues/1498#issuecomment-639768554.
> >
> > Runtime staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1219
> > Runtime Tag:
> >
> >
> https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-parent-1.3.0
> >
> > Camel K staging repository:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k/1.0.0/
> > Camel K Tag:
> >
> >
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/1.0.0
> >
> > Staging container image repository:
> > https://hub.docker.com/r/camelk/camel-k
> > /tags
> >
> > It's possible to install all staging artifacts with a single command:
> > kamel install --operator-image=camelk/camel-k:1.0.0 --maven-repository=
> > https://repository.apache.org/content/repositories/orgapachecamel-1219
> >  --olm=false
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel K 1.0.0 and Apache Camel K
> > Runtime
> > 1.3.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Nicola Ferraro
> >
>
-- 
--
Luca Burgazzoli

Re: camel-k: switch to Quarkus as default framework for integrations

[Luca Burgazzoli]

On Fri, Jun 5, 2020 at 4:14 PM Zheng Feng  wrote:

> +1 But it looks like not all of the camel components have been available on
> the camel-quarkus. Would this be a problem ?
>

I don't see this as a severe issue as it is just a matter of time and we
can at least generate a JVM only extension of every missing component.


> On Fri, Jun 5, 2020 at 7:51 PM Luca Burgazzoli 
> wrote:
>
> > Hello everyone,
> >
> > When we started working on camel-k, we haven't found any
> runtime/framework
> > that could cope with the type of workloads we had in mind for camel-k so
> we
> > ended up rolling our own framework but later on the Quarkus project has
> > started and that has changed a little the landscape as the Quarkus goal
> is
> > to support the very same cloud native workload swe want to support so we
> > have added support for Quarkus in camel-k.
> >
> > So as today we have two runtimes on which integrations can run:
> > - our in-house one based on camel-main
> > - a Quarkus based one that leverages the camel-quarkus project
> >
> > Here I'm proposing that after camel-k 1.0.0 we'll drop support for the
> > in-house framework and focus our effort on making Quarkus the foundation
> > for camel-k runtimes (the integrations) as:
> >
> > 1. Maintaining the two runtimes is becoming a challenge as a lot of
> > features we want are already provided by Quarkus and to make the runtimes
> > on par we need to develop the same set of features on our in-house
> > framework (think about health checks, integration with tracing and
> > monitoring, security, etc.). For the end-users it is also confusing as
> the
> > two runtimes have a different set of configuration options so even if
> > there's no difference between how routes are written using one or the
> other
> > runtime is not completely transparent.
> >
> > 2. Quarkus offers faster startup and reduced memory footprint by moving
> > some of the initialization at build time which copes perfectly with our
> > camel-k design as we can make optimized images once and re-use them for a
> > number of integrations.
> >
> > 3. Quarkus and the Camel Quarkus subproject can help us to leverage
> native
> > compilation when possible which fits perfectly with the serverless
> workload
> > we want camel-k to target.
> >
> >
> > What do you think ?
> >
> >
> >
> >
> >
> >
> > ---
> > Luca Burgazzoli
> >
>

camel-k: switch to Quarkus as default framework for integrations

[Luca Burgazzoli]

Hello everyone,

When we started working on camel-k, we haven't found any runtime/framework
that could cope with the type of workloads we had in mind for camel-k so we
ended up rolling our own framework but later on the Quarkus project has
started and that has changed a little the landscape as the Quarkus goal is
to support the very same cloud native workload swe want to support so we
have added support for Quarkus in camel-k.

So as today we have two runtimes on which integrations can run:
- our in-house one based on camel-main
- a Quarkus based one that leverages the camel-quarkus project

Here I'm proposing that after camel-k 1.0.0 we'll drop support for the
in-house framework and focus our effort on making Quarkus the foundation
for camel-k runtimes (the integrations) as:

1. Maintaining the two runtimes is becoming a challenge as a lot of
features we want are already provided by Quarkus and to make the runtimes
on par we need to develop the same set of features on our in-house
framework (think about health checks, integration with tracing and
monitoring, security, etc.). For the end-users it is also confusing as the
two runtimes have a different set of configuration options so even if
there's no difference between how routes are written using one or the other
runtime is not completely transparent.

2. Quarkus offers faster startup and reduced memory footprint by moving
some of the initialization at build time which copes perfectly with our
camel-k design as we can make optimized images once and re-use them for a
number of integrations.

3. Quarkus and the Camel Quarkus subproject can help us to leverage native
compilation when possible which fits perfectly with the serverless workload
we want camel-k to target.


What do you think ?






---
Luca Burgazzoli

Re: [HEADS UP] - HealthCheck work

[Luca Burgazzoli]

That's a really great work Claus

---
Luca Burgazzoli


On Wed, Jun 3, 2020 at 8:41 PM Claus Ibsen  wrote:

> Hi
>
> If you have seen the last week commits from my hand then they have
> been related to the refactoring of the health-check in Camel. There
> has been some gtliches and sorry for not noticing camel-consul got
> broken.
>
> However the work is reaching a stage where we will have the same set
> of built in health checks out of the box, that are enabled if you add
> camel-health on the classpath. (and for camel-quarkus its the
> microprofile-health).
>
> These health checks also allows to be configured in the same uniform
> way in application.properties (for example).
>
> So if you look in this example (standalone)
>
> https://github.com/apache/camel-examples/blob/master/examples/camel-example-main-health/src/main/resources/application.properties
>
> Then those options for camel.health are similar for camel on spring
> boot, quarkus, and main etc.
>
> The work for spring boot is pending and I need to do something similar
> as we have done in camel-microprofile to bridge from camel health
> check to spring boot actuator.
>
> The health check also has integration with the supervised route
> controller, so it allows the controller to mark a route that would not
> startup (after all its restart attempts faiiled) is either DOWN or in
> UNKNOWN state (you can decide).
>
> Also the health checks is JMX manageable, and as well you can access
> it via its Java API.
>
> The health checks also has the concept of readiness and liveness so
> they work great on kubernetes and in the cloud.
>
> There is some more work to add a bit more DEBUG logging to have a bit
> more visibility for troubleshooting. And for standalone mode we could
> consider to have a thin HTTP API to allow to use platform-http
> component to service a /health URL to make it easy to run in
> standalone mode and have a HTTP URL to query the state.
>
> I would also like to log on startup which health checks are discovered
> and in use.
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: [VOTE] Release Apache Camel Quarkus 1.0.0-CR2

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Mon, Jun 1, 2020 at 12:23 PM Nicola Ferraro  wrote:

> +1 (binding)
>
> Nicola
>
> On Mon, Jun 1, 2020 at 10:00 AM Andrea Cosentino
>  wrote:
>
> > +1 (binding)
> >
> > --
> > Andrea Cosentino
> > --
> > Apache Camel PMC Chair
> > Apache Karaf Committer
> > Apache Servicemix PMC Member
> > Email: ancosen1...@yahoo.com
> > Twitter: @oscerd2
> > Github: oscerd
> >
> >
> >
> >
> >
> >
> > On Friday, May 29, 2020, 07:37:01 PM GMT+2, Peter Palaga <
> > ppal...@redhat.com> wrote:
> >
> >
> >
> >
> >
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 1.0.0-CR2 (a followup of
> > the scrapped 1.0.0-CR1). Thanks Luca for fixing the dependency issue!
> >
> > Highlights (same as 1.0.0-CR1):
> > * Camel 3.3.0
> > * Quarkus 1.5.0.Final
> > * Fixed issues:
> > https://github.com/apache/camel-quarkus/milestone/2?closed=1
> >
> > Unfortunately, the standard staging repository URL
> > https://repository.apache.org/content/repositories/orgapachecamel-1218
> > is broken again.
> > I filed a new issue: https://issues.apache.org/jira/browse/INFRA-20354
> >
> > Fortunately it is possible to use
> >
> >
> https://repository.apache.org/service/local/repositories/orgapachecamel-1218/content
> > as a replacement for testing with Maven.
> > I am sorry for the inconvenience.
> >
> >
> > Tag:
> >
> >
> https://gitbox.apache.org/repos/asf?p=camel-quarkus.git;a=tag;h=ab978a8de2059f3be4ddf32c40265940e1220f0b
> >
> > Source release package:
> >
> >
> https://repository.apache.org/service/local/repositories/orgapachecamel-1218/content/org/apache/camel/quarkus/camel-quarkus/1.0.0-CR2/camel-quarkus-1.0.0-CR2-src.zip
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel Quarkus 1.0.0-CR2
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> >
> > -- Peter
> >
> >
>

Re: [VOTE] Timer reset; Release Apache Camel-Quarkus 1.0.0-CR1

[Luca Burgazzoli]

Peter,

do you have time to cancel the vote and perform a new release ?

---
Luca Burgazzoli


On Fri, May 29, 2020 at 4:41 PM Claus Ibsen  wrote:

> On Fri, May 29, 2020 at 3:59 PM Luca Burgazzoli 
> wrote:
> >
> > I've unfortunately found a blocking issue [1] and provided a related PR
> [2]
> > I think we should cancel this vote and do a new release.
> >
>
> Yeah I am okay with this. Getting JAXB properly removed and fixed is
> great for making camel-quarkus small, fast and light.
> Ideally if we could cut the release today/tomorrow so we have it to be
> released soonish.
> People can still these these binaries while a new one is being made.
>
> > [1] https://github.com/apache/camel-quarkus/issues/1275
> > [2] https://github.com/apache/camel-quarkus/pull/1276
> >
> > ---
> > Luca Burgazzoli
> >
> >
> > On Fri, May 29, 2020 at 3:14 PM Alex Dettinger 
> > wrote:
> >
> > > +1 (bindng)
> > >
> > > Just filed https://github.com/apache/camel-quarkus/issues/1274, but
> looks
> > > minor,
> > > Alex
> > >
> > > On Fri, May 29, 2020 at 2:29 PM Jean-Baptiste Onofre 
> > > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > > Le 29 mai 2020 à 12:05, Luca Burgazzoli  a
> > > écrit
> > > > :
> > > > >
> > > > > I've been able to test the 1.0.0-CR1 against camel-k-runtime and
> > > > everything
> > > > > seems fine so here by +1 (binding)
> > > > >
> > > > > ---
> > > > > Luca Burgazzoli
> > > > >
> > > > >
> > > > > On Thu, May 28, 2020 at 8:37 PM Peter Palaga 
> > > wrote:
> > > > >
> > > > >> The staging repo
> > > > >>
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1216/
> > > > >> works now thanks to ASF infra team. -- P
> > > > >>
> > > > >> On 28/05/2020 17:28, Peter Palaga wrote:
> > > > >>> Hi again,
> > > > >>>
> > > > >>> I found that Nexus UI displays the artifacts in the staging repo
> > > > through
> > > > >>> the following URL:
> > > > >>>
> > > > >>>
> > > > >>
> > > >
> > >
> https://repository.apache.org/service/local/repositories/orgapachecamel-1216/content
> > > > >>>
> > > > >>>
> > > > >>> It is not very comfortable for browsing, but it can be used for
> > > testing
> > > > >>> with Maven, just add something like the following to your
> > > settings.xml:
> > > > >>> https://gist.github.com/ppalaga/62c413f997fcba94966ec8fcb89776c3
> > > > >>>
> > > > >>> So I think, technically, the staging repo is verifiable and we
> can
> > > > >>> proceed with the voting.
> > > > >>>
> > > > >>> Let's reset the voting timer now so that everyone has enough
> time to
> > > > >>> check. I'll close the voting on Monday 2020-06-01 around 9:00
> a.m.
> > > CET.
> > > > >>>
> > > > >>> Thanks for your patience,
> > > > >>>
> > > > >>> -- Peter
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>> On 27/05/2020 22:02, Peter Palaga wrote:
> > > > >>>> I have filed https://issues.apache.org/jira/browse/INFRA-20343
> > > > >>>>
> > > > >>>> BTW, committers can access the staging repo over the Nexus UI
> > > > >>>> https://repository.apache.org/ with their ASF LDAP
> credentials. It
> > > > >>>> allows some basic checks. But of course, it is a very poor
> > > replacement
> > > > >>>> of a plain Maven staging repo.
> > > > >>>>
> > > > >>>> This older report
> https://issues.sonatype.org/browse/OSSRH-19080
> > > > >>>> recommends either to ignore the unavailability of the staging
> repo
> > > > >>>> (because the release operation works as expected after that) or
> > > deploy
> > > > >>>> anew.
> > > > >>&g

Re: [VOTE] Timer reset; Release Apache Camel-Quarkus 1.0.0-CR1

[Luca Burgazzoli]

I've unfortunately found a blocking issue [1] and provided a related PR [2]
I think we should cancel this vote and do a new release.

[1] https://github.com/apache/camel-quarkus/issues/1275
[2] https://github.com/apache/camel-quarkus/pull/1276

---
Luca Burgazzoli


On Fri, May 29, 2020 at 3:14 PM Alex Dettinger 
wrote:

> +1 (bindng)
>
> Just filed https://github.com/apache/camel-quarkus/issues/1274, but looks
> minor,
> Alex
>
> On Fri, May 29, 2020 at 2:29 PM Jean-Baptiste Onofre 
> wrote:
>
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > > Le 29 mai 2020 à 12:05, Luca Burgazzoli  a
> écrit
> > :
> > >
> > > I've been able to test the 1.0.0-CR1 against camel-k-runtime and
> > everything
> > > seems fine so here by +1 (binding)
> > >
> > > ---
> > > Luca Burgazzoli
> > >
> > >
> > > On Thu, May 28, 2020 at 8:37 PM Peter Palaga 
> wrote:
> > >
> > >> The staging repo
> > >>
> https://repository.apache.org/content/repositories/orgapachecamel-1216/
> > >> works now thanks to ASF infra team. -- P
> > >>
> > >> On 28/05/2020 17:28, Peter Palaga wrote:
> > >>> Hi again,
> > >>>
> > >>> I found that Nexus UI displays the artifacts in the staging repo
> > through
> > >>> the following URL:
> > >>>
> > >>>
> > >>
> >
> https://repository.apache.org/service/local/repositories/orgapachecamel-1216/content
> > >>>
> > >>>
> > >>> It is not very comfortable for browsing, but it can be used for
> testing
> > >>> with Maven, just add something like the following to your
> settings.xml:
> > >>> https://gist.github.com/ppalaga/62c413f997fcba94966ec8fcb89776c3
> > >>>
> > >>> So I think, technically, the staging repo is verifiable and we can
> > >>> proceed with the voting.
> > >>>
> > >>> Let's reset the voting timer now so that everyone has enough time to
> > >>> check. I'll close the voting on Monday 2020-06-01 around 9:00 a.m.
> CET.
> > >>>
> > >>> Thanks for your patience,
> > >>>
> > >>> -- Peter
> > >>>
> > >>>
> > >>>
> > >>> On 27/05/2020 22:02, Peter Palaga wrote:
> > >>>> I have filed https://issues.apache.org/jira/browse/INFRA-20343
> > >>>>
> > >>>> BTW, committers can access the staging repo over the Nexus UI
> > >>>> https://repository.apache.org/ with their ASF LDAP credentials. It
> > >>>> allows some basic checks. But of course, it is a very poor
> replacement
> > >>>> of a plain Maven staging repo.
> > >>>>
> > >>>> This older report https://issues.sonatype.org/browse/OSSRH-19080
> > >>>> recommends either to ignore the unavailability of the staging repo
> > >>>> (because the release operation works as expected after that) or
> deploy
> > >>>> anew.
> > >>>>
> > >>>> Let's see what the ASF infra says.
> > >>>>
> > >>>> -- P
> > >>>>
> > >>>> On 27/05/2020 17:44, Andrea Cosentino wrote:
> > >>>>> I think INFRA has some troubles in the last days.
> > >>>>>
> > >>>>> Syncing between Apache Repo and Maven Central is not working and
> > >>>>> there are similar cases to this release, like
> > >>>>> this
> > >>
> >
> https://issues.apache.org/jira/browse/INFRA-20334?jql=project%20%3D%20INFRA%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC
> > >>>>>
> > >>>>>
> > >>>>> @Peter Palaga I think you should open an issue to INFRA for this
> and
> > >>>>> see what we'll be their response.
> > >>>>>
> > >>>>> I know they updated Nexus too.
> > >>>>>
> > >>>>> Usually even if the repository is closed, it should be possible to
> > >>>>> use it in any application by pointing it..
> > >>>>>
> > >>>>> There is definitely something wrong, but on the INFRA side.
> > >>>>>
> > >>>>> --
> > >>>>> Andrea Cosentino
> > >