Re: [VOTE] Release Apache Camel K 2.3.2

[Otavio Rodolfo Piske]

+1 (binding)

On Thu, May 23, 2024 at 6:48 PM Zineb Bendhiba 
wrote:

> +1 (binding)
>
> Le mar. 21 mai 2024 à 12:10, Pasquale Congiusti <
> pasquale.congiu...@gmail.com> a écrit :
>
> > Hello,
> >
> > This is a vote to release Apache Camel K 2.3.2. This release provides
> some
> > bug fixes reported in the latest release 2.3.2 [1] due to certain
> > regressions introduced in version 2.3.1.
> >
> > Camel K release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k/2.3.2/
> >
> > Camel K Tag:
> > https://github.com/apache/camel-k/releases/tag/v2.3.2
> >
> > Camel K CRD Java dependency staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1713/
> >
> > Staging container image repository (multi architecture manifest):
> >
> >
> https://hub.docker.com/layers/camelk/camel-k/2.3.2/images/sha256-8d8f86bdedfe7bcc7063eea321d8eff3193ecc9cdaecbeae662f2900c2244fc6?context=explore
> >
> > It's possible to install all staging artifacts with a single command
> > (preferably using the kamel CLI you find in Camel K release files):
> >
> > $ kamel install --operator-image=camelk/camel-k:2.3.2 --olm=false
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release Apache Camel K 2.3.2
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > I start the vote with my +1.
> >
> > Thanks and regards,
> > Pasquale Congiusti
> >
> > [1] https://github.com/apache/camel-k/milestone/51?closed=1
> >
>
>
> --
> Zineb Bendhiba
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel Quarkus 3.11.0

[Otavio Rodolfo Piske]

+1 (binding)

On Fri, May 24, 2024 at 9:40 AM Claus Ibsen  wrote:

> +1 (binding)
>
> On Fri, May 24, 2024 at 7:46 AM Peter Palaga  wrote:
>
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 3.11.0.
> >
> > Highlights:
> >
> > * Camel 4.6.0
> > * Quarkus 3.11.0
> >
> > All commits:
> >
> > https://github.com/apache/camel-quarkus/compare/3.10.0...3.11.0
> >
> > Staging repository:
> >
> > https://repository.apache.org/content/repositories/orgapachecamel-1714
> >
> > Tag:
> >
> > https://github.com/apache/camel-quarkus/releases/tag/3.11.0
> >
> > Source release package + SBOM:
> >
> > https://dist.apache.org/repos/dist/dev/camel/camel-quarkus/3.11.0/
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binaries as Apache Camel Quarkus 3.11.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> >
> >
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release of Apache Camel Karavan 4.6.0

[Otavio Rodolfo Piske]

+1 (binding)

On Thu, May 23, 2024 at 6:48 PM Zineb Bendhiba 
wrote:

> +1 (binding)
>
>
> Le mar. 21 mai 2024 à 20:28, Marat Gubaidullin <
> marat.gubaidul...@gmail.com>
> a écrit :
>
> > Dear Camel Developers,
> >
> > This is a vote for the release of Apache Camel Karavan version 4.6.0.
> >
> > Developer Experience improvements:
> >
> >1. ErrorHandler configuration on Route level
> >2. LoadBalance EIP
> >3. Container image and commit information in UI for running
> integration
> >project
> >4. Build script simplified clone Git repo
> >5. User can create Kamelet in project
> >6. User can configure REST DSL with OpenApi contract
> >
> > Latest versions:
> >
> >1. Camel 4.6.0
> >2. Kamelets 4.6.0
> >3. Jkube 1.16.2
> >4. JBang v0.116.0
> >
> > Source release package:
> > https://dist.apache.org/repos/dist/dev/camel/camel-karavan/4.6.0/
> >
> > Some files in the codebase have missing licence headers still. This is
> done
> > intentionally, because these files are code snippets/templates used to
> > generate user's code.
> >
> > VS Code Extension
> > https://github.com/apache/camel-karavan/releases/tag/4.6.0
> >
> > We encourage all Camel contributors to participate in this release vote.
> > Your feedback and contributions play a crucial role in making Apache
> Camel
> > Karavan better with each release.
> >
> > Please cast your vote by replying to this email with your decision:
> > [ ] +1 Release
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The voting period will remain open for 72 hours.
> >
> > Thank you for your continued support and dedication to the Apache Camel
> > project.
> >
> > My +1 (binding) is here
> >
> > Have a nice day,
> > Marat
> >
>
>
> --
> Zineb Bendhiba
>


-- 
Otavio R. Piske
http://orpiske.net

Re: new contributor

[Otavio Rodolfo Piske]

My previous message seems to have bounced, so sending it again ...

The correct Job URL to watch for test results is
https://ci-builds.apache.org/blue/organizations/jenkins/Camel%2FCamel%20Core%20(Build%20and%20test)/activity/

The old Camel Core jobs, one for each platform, have been consolidated into
a matrix one.

Kind regards

On Tue, May 14, 2024 at 7:06 PM Aurélien Pupier  wrote:

> Hello,
>
> the Apache Camel CI is here https://ci-builds.apache.org/job/Camel/
> After merge on Camel core, you can look to
> https://ci-builds.apache.org/job/Camel/job/Camel%20JDK21/job/main/
>
> Regards,
>
>
> On Tue, May 14, 2024 at 5:58 PM Antoine  wrote:
>
> > Hi,
> >
> > My first contribution has been merged 3 weeks ago:
> > https://github.com/apache/camel/pull/13871.
> > Before starting with my next contribution I wanted to follow it on Apache
> > CI as documented on the contributing page but could not find where to
> look.
> > In the meantime I saw my change merged in 4.6.x.
> > Where should I look to be sure I didn't break anything after a PR merge?
> >
> > Antoine Wils
> >
> > On Wed, Apr 17, 2024 at 3:13 PM Alexandre Gallice  >
> > wrote:
> >
> > > Welcome Antoine, we love contributions here. In case people are
> searching
> > > for help when starting contributions, then there is this guide which is
> > > good to remember.
> > >
> > > On Wed, Apr 17, 2024 at 2:38 PM Claudio Miranda <
> clau...@claudius.com.br
> > >
> > > wrote:
> > >
> > > > Feel free to work on it, however, I suggest making small changes and
> > > > asking for reviews in the pull request, so you have a better
> > > > understanding of the contribution effort.
> > > >
> > > > I also suggest issues marked with help wanted.
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/browse/CAMEL-20680?jql=project%20%3D%20CAMEL%20AND%20status%20%3D%20Open%20AND%20labels%20%3D%20help-wanted
> > > >
> > > > Em ter., 16 de abr. de 2024 às 14:31, Antoine <
> antoine.w...@gmail.com>
> > > > escreveu:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > I am new here and like to contribute.
> > > > > I am a Java developer and have been a Camel user for a decade.
> > > > > To get acquainted to contribute I thought of helping on CAMEL-20206
> > > > >  "Cleanup
> overly
> > > > complex
> > > > > methods".
> > > > > Is that a good way to start?
> > > > >
> > > > > Regards
> > > > >
> > > > > --
> > > > > Antoine
> > > >
> > > >
> > > >
> > > > --
> > > >   Claudio Miranda
> > > >
> > > > clau...@claudius.com.br
> > > > http://www.claudius.com.br
> > > >
> > >
> >
> >
> > --
> > Antoine
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel Kamelets 4.6.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks!

On Mon, May 13, 2024 at 3:12 PM Zineb Bendhiba 
wrote:

> +1 (binding)
>
> Le lun. 13 mai 2024 à 09:56, Andrea Cosentino  a écrit
> :
>
> > Hello all,
> >
> > This is a vote for releasing camel-kamelets 4.6.0
> >
> > This is a release supporting Camel 4.6.0
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.6.0
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1712
> > Kamelets Tag:
> > https://github.com/apache/camel-kamelets/releases/tag/v4.6.0
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 4.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
> >
>
>
> --
> Zineb Bendhiba
>


-- 
Otavio R. Piske
http://orpiske.net

Re: CI environments definition

[Otavio Rodolfo Piske]

Hi,

These are:

s390x: Linux On Mainfraime (https://en.wikipedia.org/wiki/IBM_System/390)
ppc64: Linux on 64-bit Power, with little-endian byte ordering (
https://en.wikipedia.org/wiki/Power_ISA &
https://en.wikipedia.org/wiki/Ppc64)
ubuntu: Linux on x86 running on both JDK 17 and 21.

The main CI environment is the ASF one, although we do consider the checks
/ builds running on Github Actions as an integral part of our quality
assurance process (as they focus on pre-merge contributions and some
platforms we don't have at ASF CI - such as Windows).

Kind regards

On Fri, May 10, 2024 at 3:00 PM Jang-Vijay Singh  wrote:

> Dear all,
>
> Is it possible to know what the precise specification and configuration of
> these environments is, and how many CI environments there are?
>
> e.g.
> s390x
> ppc64
> ubuntu
>
> I am new to contributing to Camel, so not very intuitively familiar with
> these architectures.
> One particular issue related to sporadic test failures on some ASF CI
> environments really interested me, so I was trying to contribute.
>
> Best regards,
> JV
>


-- 
Otavio R. Piske
http://orpiske.net

Clarifying the contribution guidelines

[Otavio Rodolfo Piske]

Hello everyone,

The recent attacks on open source projects, by malicious actors trying to
obtain privileged access to the repositories and injecting malicious code
has been pretty frightening. Just recently we had an influx of short-lived
accounts (just a few days old and likely fake) trying to submit "cleanups"
to the code base without any discussion with the community.

I think it would be important for us to clarify what we expect from anyone
contributing to Apache Camel and what other committers should look at when
reviewing contributions.

Please note that many of the additions to the document are things that we
already expect, but have never been formalized before.

I have discussed this with a few others about this (Claus, Andrea) and I
think it's time to bring it to the community for review and discussion.

I have opened the following PR with the updated details:
https://github.com/apache/camel/pull/14131.

Please review and share your thoughts.

Kind regards
-- 
Otavio R. Piske
http://orpiske.net

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

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Gregor!

On Tue, Apr 23, 2024 at 2:54 PM Claus Ibsen  wrote:

> +1 (binding)
>
> On Tue, Apr 23, 2024 at 10:01 AM Gregor Zurowski  >
> wrote:
>
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 4.0.5, a new patch release with
> > 18 improvements and fixes.
> >
> > Release notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353858=12311211
> >
> > == Apache Camel 4.0.5 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1698/
> >
> > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1698/org/apache/camel/camel/4.0.5/
> >
> > Tag: https://github.com/apache/camel/releases/tag/camel-4.0.5
> >
> > == Apache Camel Spring Boot 4.0.5 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1699/
> >
> > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1699/org/apache/camel/springboot/spring-boot/4.0.5/
> >
> > Tag:
> >
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.0.5
> >
> > Please test this release candidate and cast your vote:
> > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.0.5
> > [ ] -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
>


-- 
Otavio R. Piske
http://orpiske.net

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

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Gregor!

On Sun, Apr 21, 2024 at 7:47 PM Gregor Zurowski 
wrote:

> Hi Everyone:
>
> This is a vote to release Apache Camel 4.4.2, a new patch release with
> 31 fixes and improvements.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12354402=12311211
>
> == Apache Camel 4.4.2 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1695/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1695/org/apache/camel/apache-camel/4.4.2/
>
> Tag: https://github.com/apache/camel/releases/tag/camel-4.4.2
>
> == Apache Camel Spring Boot 4.4.2 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1696/
>
> Tag:
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.4.2
>
> Please test this release candidate and cast your vote:
> [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.4.2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Camel 4.0.5 Release in May

[Otavio Rodolfo Piske]

+1 from me.

Thanks!

On Fri, Apr 19, 2024 at 9:46 AM Andrea Cosentino
 wrote:

> +1 from my side.
> --Andrea Cosentino --Apache Camel PMC
> ChairApache Karaf CommitterApache Servicemix PMC MemberEmail:
> ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd
>
> On Thursday, April 18, 2024 at 10:27:47 PM GMT+2, Claus Ibsen <
> claus.ib...@gmail.com> wrote:
>
>  Hi
>
> After the 4.4.2 release, we could just as well do a patch release for
> 4.0.5.
> We have upgraded to the latest spring boot and the branch is also ready for
> cutting a release.
>
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>



-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release of Apache Camel Karavan 4.5.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Marat!

On Mon, Apr 15, 2024 at 1:56 PM Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> Regards
> JB
>
> On Sun, Apr 14, 2024 at 10:40 PM Marat Gubaidullin
>  wrote:
> >
> > Dear Camel Developers,
> >
> > This is a vote for the release of Apache Camel Karavan version 4.5.0.
> >
> > Developer Experience improvements:
> >
> >1. List of Exchange Properties for EIP in Properties Panel
> >2. Exchange Variables and Functions docs for mostly used Expression
> >Languages in Editor
> >3. During installation Templates created only for the container
> >management used (Docker, Kubernetes, Openshift)
> >4. Automatic created ConfigMaps for build script in Kubernetes
> >5. Preferred Element in Component/Kamelet/EIP Palette (more used =
> >preferred)
> >6. User can delete Preferred Element in Component/Kamelet/EIP Palette
> >7. In devmode Trace window contains Exchange Body, Headers, Properties
> >and variables
> >
> > Latest versions:
> >
> >1. Camel 4.5.0
> >2. Kamelets 4.5.0
> >3. Jkube 1.16.2
> >4. JBang v0.116.0
> >
> > Source release package:
> > https://dist.apache.org/repos/dist/dev/camel/camel-karavan/4.5.0/
> >
> > Some files in the codebase have missing licence headers still. This is
> done
> > intentionally, because these files are code snippets/templates used to
> > generate user's code.
> >
> > VS Code Extension
> > https://github.com/apache/camel-karavan/releases/tag/4.5.0
> >
> > We encourage all Camel contributors to participate in this release vote.
> > Your feedback and contributions play a crucial role in making Apache
> Camel
> > Karavan better with each release.
> >
> > Please cast your vote by replying to this email with your decision:
> > [ ] +1 Release
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The voting period will remain open for 72 hours.
> >
> > Thank you for your continued support and dedication to the Apache Camel
> > project.
> >
> > My +1 is here
> >
> > Have a nice day,
> > Marat
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Camel 4.4.2 release by end of April

[Otavio Rodolfo Piske]

+1 from me.

Thanks!

On Mon, Apr 15, 2024 at 1:58 PM Jean-Baptiste Onofré 
wrote:

> Hi Claus,
>
> Yeah, it makes sense to me.
>
> Regards
> JB
>
> On Mon, Apr 15, 2024 at 6:49 AM Claus Ibsen  wrote:
> >
> > Hi
> >
> > I think it would be good to get this branch ready this week, so Gregor
> can
> > cut the release when he has time.
> >
> >
> > On Fri, Mar 29, 2024 at 6:57 PM Claus Ibsen 
> wrote:
> >
> > > Hi
> > >
> > > I think it would be good to cut a new 4.4.2 LTS patch to be released
> > > towards the end of April.
> > > Gregor is out of town for 2 weeks, so that should be okay. When he
> returns
> > > we can bring him into the loop of finding time to cut this release.
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -
> > > @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel K 2.3.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks!

On Wed, Apr 3, 2024 at 11:10 AM Claus Ibsen  wrote:

> +1 (binding)
>
> On Tue, Apr 2, 2024 at 4:46 PM Pasquale Congiusti <
> pasquale.congiu...@gmail.com> wrote:
>
> > Hello,
> >
> > This is a vote to release Apache Camel K 2.3.0. This release provides
> many
> > new features [1] and sets the default runtime to Camel Quarkus 3.8.1
> (based
> > on Camel 4.4.1).
> >
> > Camel K release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k/2.3.0/
> >
> > Camel K Tag:
> > https://github.com/apache/camel-k/releases/tag/v2.3.0
> >
> > Camel K CRD Java dependency staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1693/
> >
> > Staging container image repository (multi architecture manifest):
> >
> >
> https://hub.docker.com/layers/camelk/camel-k/2.3.0/images/sha256-a043af04c9b816f0dfd5db64ba69bae192d73dd726df83aaf2002559a111a786?context=explore
> >
> > It's possible to install all staging artifacts with a single command
> > (preferably using the kamel CLI you find in Camel K release files):
> >
> > $ kamel install --operator-image=camelk/camel-k:2.3.0 --olm=false
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release Apache Camel K 2.3.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > I start the vote with my +1.
> >
> > Thanks and regards,
> > Pasquale Congiusti
> >
> > [1] https://github.com/apache/camel-k/milestone/48?closed=1
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Camel K Runtime 3.8.1

[Otavio Rodolfo Piske]

+1 (binding)

Thanks!

On Mon, Mar 25, 2024 at 1:35 PM Claus Ibsen  wrote:

> +1 (binding)
>
> On Mon, Mar 25, 2024 at 12:14 PM Pasquale Congiusti <
> pasquale.congiu...@gmail.com> wrote:
>
> > Hello,
> >
> > This is a vote to release Camel K Runtime 3.8.1. This release will
> provide
> > the runtime for Camel Quarkus 3.8.1 (based on Camel 4.4.1) and include a
> > change in the catalog which will allow the Camel K Operator to be
> > completely independent from the runtime for the trait configuration.
> >
> > Camel K Runtime source files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/3.8.1/
> >
> > Camel K Runtime staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1691
> >
> > Camel K Runtime Tag:
> >
> >
> https://github.com/apache/camel-k-runtime/releases/tag/camel-k-runtime-project-3.8.1
> >
> > It's possible test the staging artifacts by installing the latest Camel K
> > CLI (kamel) with the staging repository and run any Integration with the
> > new runtime:
> >
> > -
> > kamel install --maven-repository=
> > https://repository.apache.org/content/repositories/orgapachecamel-1691
> > ...
> >
> > kamel run Test.java -t camel.runtime-version=3.8.1
> > -
> >
> > Please test these release candidates and cast your vote.
> >
> > [ ] +1 Release Apache Camel K Runtime 3.8.1
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > I start the vote with my +1.
> >
> > Thanks and regards,
> > Pasquale Congiusti
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel 4.5.0

[Otavio Rodolfo Piske]

+1 (binding)

Tested on my own CI ... I found no issues or problems.

Thanks Gregor!

On Mon, Mar 25, 2024 at 4:34 PM Jon Anstey  wrote:

> +1 (binding)
>
> Thanks Gregor!
>
> On Sun, Mar 24, 2024 at 7:00 AM Gregor Zurowski 
> 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
> >
>
>
> --
> Cheers,
> Jon
> ---
> Red Hat, Inc.
> Email: jans...@redhat.com
> Web: http://redhat.com
> Twitter: jon_anstey
> Blog: http://janstey.blogspot.com
> Camel in Action:
> https://www.manning.com/books/camel-in-action-second-edition
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel Quarkus 3.9.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Alexandre!

On Fri, Mar 22, 2024 at 6:41 PM zineb bendhiba 
wrote:

> +1 ( binding)
>
> Many thanks
>
> Zineb
>
> > Le 21 mars 2024 à 16:00, Alexandre Gallice  a
> écrit :
> >
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 3.9.0.
> >
> > Highlights:
> >
> > * Camel 4.4.1
> > * Quarkus 3.9.0
> >
> > All commits:
> >
> > https://github.com/apache/camel-quarkus/compare/3.8.0...3.9.0
> >
> > Staging repository:
> >
> > https://repository.apache.org/content/repositories/orgapachecamel-1686
> >
> > Tag:
> >
> > https://github.com/apache/camel-quarkus/releases/tag/3.9.0
> >
> > Source release package + SBOM:
> >
> > https://dist.apache.org/repos/dist/dev/camel/camel-quarkus/3.9.0/
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binaries as Apache Camel Quarkus 3.9.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Apache Camel 4.5 Release

[Otavio Rodolfo Piske]

+1 from me.

On my end, the only thing I'd like to complete is adjusting the naming for
camel-langchain-* components.

Kind regards

On Thu, Mar 21, 2024 at 9:39 AM Claus Ibsen  wrote:

> Hi Gregor
>
> Yes that is very good. Later today Spring Boot 3.2.4 is released which we
> should upgrade.
> I will tidy up the last bits today, and give an update tomorrow when we are
> ready.
>
>
>
> On Thu, Mar 21, 2024 at 9:23 AM Gregor Zurowski 
> wrote:
>
> > Hi,
> >
> > Yes, I'll be available for the release. Do you think we can start this
> > weekend?
> >
> > Thanks,
> > Gregor
> >
> > On Wed, Mar 20, 2024 at 5:18 PM Claus Ibsen 
> wrote:
> > >
> > > Hi
> > >
> > > Okay lets close down the next couple of days to get the code ready for
> > > cutting 4.5.0 release.
> > > Gregor are you able to do this in the near future?
> > >
> > >
> > >
> > > On Mon, Mar 4, 2024 at 7:15 AM Claus Ibsen 
> > wrote:
> > >
> > > > Hi
> > > >
> > > > We have good progress on the next minor release.
> > > > There is some work ongoing to simplify the maintenance of our
> generator
> > > > code we use during building Camel. After this is complete, and maybe
> > some
> > > > other stuff, then it would be good to get a 4.5.0 release out to the
> > > > community.
> > > >
> > > >
> > > >
> > > > --
> > > > Claus Ibsen
> > > > -
> > > > @davsclaus
> > > > Camel in Action 2: https://www.manning.com/ibsen2
> > > >
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -
> > > @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel Quarkus 3.8.1

[Otavio Rodolfo Piske]

+1 (binding)

Thanks James!

On Sat, Mar 16, 2024 at 5:55 PM Claudio Miranda 
wrote:

> +1 (non binding)
>
> Em sáb., 16 de mar. de 2024 às 08:18, Andrea Cosentino
>  escreveu:
> >
> > +1 (binding)
> >
> > Thanks James
> >
> > Il ven 15 mar 2024, 22:53 James Netherton  ha
> > scritto:
> >
> > > Hi,
> > >
> > > This is a vote to release Apache Camel Quarkus 3.8.1.
> > >
> > > Highlights:
> > >
> > > * Camel 4.4.1
> > > * Quarkus 3.8.3
> > >
> > > All commits:
> > >
> > > https://github.com/apache/camel-quarkus/compare/3.8.0...3.8.1
> > >
> > > Staging repository:
> > >
> > > https://repository.apache.org/content/repositories/orgapachecamel-1685
> > >
> > > Tag:
> > >
> > > https://github.com/apache/camel-quarkus/releases/tag/3.8.1
> > >
> > > Source release package + SBOM:
> > >
> > > https://dist.apache.org/repos/dist/dev/camel/camel-quarkus/3.8.1/
> > >
> > > Please test this release candidate and cast your vote.
> > >
> > > [ ] +1 Release the binaries as Apache Camel Quarkus 3.8.1
> > > [ ] -1 Veto the release (provide specific comments)
> > >
> > > The vote is open for at least 72 hours.
> > >
>
>
>
> --
>   Claudio Miranda
>
> clau...@claudius.com.br
> http://www.claudius.com.br
>


-- 
Otavio R. Piske
http://orpiske.net

CAMEL-20518: Camel builds on Windows

[Otavio Rodolfo Piske]

Folks,

Recently I noticed that Apache Camel is not building on Windows anymore.
Most of the people in my network use Linux or macOS, so I'm sending this
here to reach a larger audience.

In case anyone has access to Windows, understands the platform and want to
take a look, here's the problem we are having:

[ERROR] Failed to execute goal
org.apache.camel:camel-package-maven-plugin:4.5.0-SNAPSHOT:prepare-catalog
(default) on project camel-catalog: Error preparing catalog: Error reading
json file:
D:\a\camel\camel\catalog\camel-catalog\..\..\components\camel-salesforce\camel-salesforce-component\target\classes\META-INF\org\apache\camel\component\salesforce\salesforce.json:
Input length = 3 -> [Help 1]

I created the following ticket for this problem:
https://issues.apache.org/jira/browse/CAMEL-20518

Kind regards
-- 
Otavio R. Piske
http://orpiske.net

Re: Apache Camel 4.4.1 Release

[Otavio Rodolfo Piske]

+1

We have some documentation cleanups that would be cool to push to the LTS
documentation on the website and to our users.

Kind regards

On Mon, Mar 4, 2024 at 10:14 AM Claus Ibsen  wrote:

> Hi
>
> I think it would be good to cut our first patch release for 4.4.x LTS
> branch this month.
> Better sooner than later.
>
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Apache Camel 4.5 Release

[Otavio Rodolfo Piske]

Hi Claus, thanks for raising this.

+1 from me.

I don't really have any major items on my end. The documentation cleanups
are completed.

I have been working on cleaning up the jms tests - they have become flaky
again at some point in the last release (CAMEL-20477 + CAMEL-20478). And
I'd like to investigate CAMEL-20493.

Kind regards

On Mon, Mar 4, 2024 at 10:16 AM Claus Ibsen  wrote:

> Hi
>
> We have good progress on the next minor release.
> There is some work ongoing to simplify the maintenance of our generator
> code we use during building Camel. After this is complete, and maybe some
> other stuff, then it would be good to get a 4.5.0 release out to the
> community.
>
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release of Apache Camel Karavan 4.4.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Marat!

Otavio R. Piske

> On 1. 3. 2024, at 20:19, Andrea Cosentino  wrote:
> 
> +1 (binding)
> 
> Thanks marat
> 
> Il gio 29 feb 2024, 03:44 Marat Gubaidullin 
> ha scritto:
> 
>> Dear Camel Developers,
>> 
>> This is a vote for the release of Apache Camel Karavan version 4.4.0.
>> 
>> 
>> Designer improvements:
>> 1. Support Variables in DSLs (From, To, Marshall, Unmarshall, etc)
>> 2. New DSLs for Variables (setVariable, removeVariable, convertVariableTo)
>> 
>> 3. List of existing variables in DSL properties
>> 4. Navigation through `direct` and 'seda' between files
>> 
>> 5. Accept to properties in `application.properties` in DSL placeholders
>> 
>> 6. Create new property in `application.properties` from DSL placeholders
>> 
>> 7. Simplified Expression
>> 
>> 8. Component consumed/produced Headers in property UI
>> 
>> 
>> Web-application improvements:
>> 1. Configurable list of Components and Kamelets
>> 2. Configurable resource limits for projects in Docker
>> 3. Embedded cache instead of external
>> 4. Wizard to simply create beans (database, messaging, etc)
>> 5. Configurable Kubernetes Secrets -> Environment variables mapping for
>> build container
>> 
>> 6. Support SSH Keys for Git Authentication
>> 
>> Latest versions:
>> 1. Camel 4.4.0
>> 5. Kamelets 4.4.0
>> 7. Jkube 1.16.1
>> 8. JBang v0.114.0
>> 
>> Source release package:
>> https://dist.apache.org/repos/dist/dev/camel/camel-karavan/4.4.0/
>> 
>> Some files in the codebase have missing licence headers still. This is done
>> intentionally, because these files are code snippets/templates used to
>> generate user's code.
>> 
>> VS Code Extension
>> https://github.com/apache/camel-karavan/releases/tag/4.4.0
>> 
>> We encourage all Camel contributors to participate in this release vote.
>> Your feedback and contributions play a crucial role in making Apache Camel
>> Karavan better with each release.
>> 
>> Please cast your vote by replying to this email with your decision:
>> [ ] +1 Release
>> [ ] -1 Veto the release (provide specific comments)
>> 
>> The voting period will remain open for 72 hours.
>> 
>> Thank you for your continued support and dedication to the Apache Camel
>> project.
>> 
>> My +1 is here
>> 
>> Have a nice day,
>> Marat
>> 

Re: [VOTE] Release Apache Camel Quarkus 3.8.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks!

On Thu, Feb 22, 2024 at 11:27 AM Claudio Miranda 
wrote:

> +1 (non binding)
>
> Em qui., 22 de fev. de 2024 às 08:21, Alexandre Gallice
>  escreveu:
> >
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 3.8.0.
> >
> > Highlights:
> >
> > * Camel 4.4.0
> > * Quarkus 3.8.0
> >
> > All commits:
> >
> > https://github.com/apache/camel-quarkus/compare/3.7.0...3.8.0
> >
> > Staging repository:
> >
> > https://repository.apache.org/content/repositories/orgapachecamel-1682
> >
> > Tag:
> >
> > https://github.com/apache/camel-quarkus/releases/tag/3.8.0
> >
> > Source release package + SBOM:
> >
> > https://dist.apache.org/repos/dist/dev/camel/camel-quarkus/3.8.0/
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binaries as Apache Camel Quarkus 3.8.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
>
>
>
> --
>   Claudio Miranda
>
> clau...@claudius.com.br
> http://www.claudius.com.br
>


-- 
Otavio R. Piske
http://orpiske.net

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

[Otavio Rodolfo Piske]

+1 (binding)

Tested on my own CI. Looks good.

Thanks Gregor!

On Tue, Feb 13, 2024 at 3:48 PM Babak Vahdat
 wrote:

> +1 (binding)
>
> Thanks Gregor!
>
> --
> Babak
>
> > Am 12.02.2024 um 20:08 schrieb Gregor Zurowski  >:
> >
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 4.4.0, a new LTS release with
> > 152 new features and improvements.
> >
> > Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353989=12311211
> >
> > == Apache Camel 4.4.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1679/
> >
> > Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1679/org/apache/camel/apache-camel/4.4.0/
> >
> > Tag: https://github.com/apache/camel/releases/tag/camel-4.4.0
> >
> > == Apache Camel Spring Boot 4.4.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1680/
> >
> > Tag:
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.4.0
> >
> > Please test this release candidate and cast your vote:
> > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.4.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

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

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Andrea

On Wed, Feb 7, 2024 at 8:06 AM Babak Vahdat
 wrote:

> +1 (binding)
>
> Thanks Andrea!
>
> --
> Babak
>
> > On 6 Feb 2024, at 22:06, Andrea  wrote:
> >
> > Hello all,
> >
> > This is a vote to release Apache Camel-kafka-connector 4.0.3
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1678
> >
> > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-kafka-connector.git;a=tag;h=refs/tags/camel-kafka-connector-4.0.3
> >
> > Update to camel 4.0.3
> >
> > Please test this release candidate and cast your vote.
> > [ ] +1 Release the binary as  Apache Camel-kafka-connector 4.0.3
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Andrea.
>
>

-- 
Otavio R. Piske
http://orpiske.net

Re: Documentation improvements

[Otavio Rodolfo Piske]

Hi

"1. The guide (first link) mentions “Also add any component starters
    your Spring
   Boot application requires.”
   Unfortunately the link leads to an overview of all Camel Spring Boot
   starter dependencies which is not complete. It is e.g. missing explicit
   mentions of the “Endpoint DSL” as well as the “Component DSL” components
   and probably several more.
"

You can find the documentation for the Component DSL and Endpoint DSL in
the Camel Core documentation page: https://camel.apache.org/camel-core/.
Check the reference documentation section.

As for item #2 ... I am not sure if it's. feasible, but I am sure the
community would be happy to accept a contribution for this.

Kind regards


On Fri, Feb 2, 2024 at 3:20 PM Ja Li  wrote:

> Hi there,
>
>
>
> I found this the most fitting mailing list for my request to improve the
> documentation (especially for newcomers):
>
>
>
> The following page describes the configuration of Camel together with
> Spring Boot by suggesting to add the (curated) camel-spring-boot-bom in
> your Maven project: https://camel.apache.org/camel-spring-boot/4.0.x/
>
> I just setup a new project with the above mentioned BOM and wanted to use
> the endpoint DSL and component DSL dependencies and wondered why their
> version could not be resolved. Then I took a look on the raw BOM pom (
>
> https://repo1.maven.org/maven2/org/apache/camel/springboot/camel-spring-boot-bom/4.3.0/camel-spring-boot-bom-4.3.0.pom
> )
> and found the correct groupid and artifactid.
>
>
>
>1. The guide (first link) mentions “Also add any component starters
> your
> Spring
>Boot application requires.”
>Unfortunately the link leads to an overview of all Camel Spring Boot
>starter dependencies which is not complete. It is e.g. missing explicit
>mentions of the “Endpoint DSL” as well as the “Component DSL” components
>and probably several more.
>2. Also the documentation pages of those components (unlike others)
>itself only mention the Maven dependency information for their
> non-starter
>version:
>
> https://camel.apache.org/manual/Endpoint-dsl.html#_dependency
>
> https://camel.apache.org/manual/component-dsl.html#_dependency
>
>
>
> Therefore my request is to
>
>1. complete the list/overview of Camel Spring Boot starters or (maybe
>even better) atleast add a warning to it that it is currently not
> complete
>and users should be aware to search in their used BOM .pom file for the
>existence of a starter version of their desired component.
>2. also add the starter-version dependency information to the respective
>component documentation pages.
>
>
> Thanks for feedback and kind regards
>
> Jacob
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel 4.0.4

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Gregor

On Mon, Jan 29, 2024 at 11:08 AM Gaëlle Fournier <
gaelle.fournier.w...@gmail.com> wrote:

> +1 (non-binding)
>
> Thanks!
>
> ---
> Gaëlle
>
> Le dim. 28 janv. 2024 à 20:47, Gregor Zurowski 
> a
> écrit :
>
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 4.0.4, a new patch release with
> > 23 improvements and fixes.
> >
> > Release notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353858=12311211
> >
> > == Apache Camel 4.0.4 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1676/
> >
> > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1676/org/apache/camel/camel/4.0.4/
> >
> > Tag: https://github.com/apache/camel/releases/tag/camel-4.0.4
> >
> > == Apache Camel Spring Boot 4.0.4 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1677/
> >
> > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1677/org/apache/camel/springboot/spring-boot/4.0.4/
> >
> > Tag:
> >
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.0.4
> >
> > Please test this release candidate and cast your vote:
> > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.0.4
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
> >
>


-- 
Otavio R. Piske
http://orpiske.net

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

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Gregor!

On Fri, Jan 26, 2024 at 7:29 PM Nicolas Filotto
 wrote:

> +1 (binding)
>
> Envoyé à partir de Outlook pour iOS
> 
> De : Claus Ibsen 
> Envoyé : Friday, January 26, 2024 6:11:49 PM
> À : dev@camel.apache.org 
> Objet : Re: [VOTE] Release Apache Camel 3.22.1 (LTS)
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
>
> +1 (binding)
>
> On Fri, Jan 26, 2024 at 5:51 PM Gregor Zurowski 
> wrote:
>
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 3.22.1, a new patch release
> > with 8 improvements and fixes.
> >
> > Release notes:
> >
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fsecure%2FReleaseNote.jspa%3Fversion%3D12354118%26projectId%3D12311211=05%7C02%7CNicolas.Filotto%40qlik.com%7C4fa47d8586044c85c5d808dc1e91eed9%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638418859347459637%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=73pDNv6ukkKtxM6ZMzy6OSrW890MJDfSUQ2W4E4dERk%3D=0
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12354118=12311211
> >
> >
> > == Apache Camel 3.22.1 ==
> >
> > Staging repository:
> >
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachecamel-1673%2F=05%7C02%7CNicolas.Filotto%40qlik.com%7C4fa47d8586044c85c5d808dc1e91eed9%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638418859347466834%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=2IwrXE8HNUTXxmL4lpEi5s11f4qTbFBHCAZ56P1bnKw%3D=0
> 
> >
> > Tarballs:
> >
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachecamel-1673%2Forg%2Fapache%2Fcamel%2Fapache-camel%2F3.22.1%2F=05%7C02%7CNicolas.Filotto%40qlik.com%7C4fa47d8586044c85c5d808dc1e91eed9%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638418859347470706%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=CkOV1dz04aDrnAJJo2KilrHZ4Z%2Fj6qmG5yh2bYLymBQ%3D=0
> <
> https://repository.apache.org/content/repositories/orgapachecamel-1673/org/apache/camel/apache-camel/3.22.1/
> >
> >
> > Tag:
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fcamel%2Freleases%2Ftag%2Fcamel-3.22.1=05%7C02%7CNicolas.Filotto%40qlik.com%7C4fa47d8586044c85c5d808dc1e91eed9%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638418859347474358%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=s7frxXgoCz5VRO8br3IHLN9iE5fS7TGc1EBIebM0jBY%3D=0
> 
> >
> > == Apache Camel Spring Boot 3.22.1 ==
> >
> > Staging repository:
> >
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachecamel-1674%2F=05%7C02%7CNicolas.Filotto%40qlik.com%7C4fa47d8586044c85c5d808dc1e91eed9%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638418859347477839%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=6rTjU4hcRj5KgOhNtZk4imsh2D%2B0Y7oQrJFJlJKbLQw%3D=0
> 
> >
> > Tag:
> >
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fcamel-spring-boot%2Freleases%2Ftag%2Fcamel-spring-boot-3.22.1=05%7C02%7CNicolas.Filotto%40qlik.com%7C4fa47d8586044c85c5d808dc1e91eed9%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638418859347481227%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=ItMF%2FMer4zF%2BCI7ZmHyOa3IVWUhU5hN1CiABX98S780%3D=0
> <
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.22.1
> >
> >
> > == Apache Camel Karaf 3.22.1 ==
> >
> > Staging repository:
> >
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachecamel-1675%2F=05%7C02%7CNicolas.Filotto%40qlik.com%7C4fa47d8586044c85c5d808dc1e91eed9%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638418859347484606%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=TFNq0QgeiD9urlgkiuKDNSzFq%2FjukMuV4kYEQYg%2BzTo%3D=0
> 
> >
> > Tag:
> 

Re: [VOTE] Release Apache Camel Quarkus 3.7.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks James!

On Fri, Jan 26, 2024 at 4:31 PM Gaëlle Fournier <
gaelle.fournier.w...@gmail.com> wrote:

> +1 (non-binding)
>
> Thanks!
>
> ---
> Gaëlle
>
> Le jeu. 25 janv. 2024 à 17:23, James Netherton 
> a
> écrit :
>
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 3.7.0.
> >
> > Highlights:
> >
> > * Camel 4.3.0
> > * Quarkus 3.7.0
> >
> > All commits:
> >
> > https://github.com/apache/camel-quarkus/compare/3.6.0...3.7.0
> >
> > Staging repository:
> >
> > https://repository.apache.org/content/repositories/orgapachecamel-1672
> >
> > Tag:
> >
> > https://github.com/apache/camel-quarkus/releases/tag/3.7.0
> >
> > Source release package + SBOM:
> >
> > https://dist.apache.org/repos/dist/dev/camel/camel-quarkus/3.7.0/
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binaries as Apache Camel Quarkus 3.7.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
>


-- 
Otavio R. Piske
http://orpiske.net

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

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Gregor!

On Fri, Jan 26, 2024 at 4:30 PM Gaëlle Fournier <
gaelle.fournier.w...@gmail.com> wrote:

> +1 (non binding)
>
> Thanks!
>
> ---
> Gaëlle
>
> Le jeu. 25 janv. 2024 à 10:20, Gregor Zurowski 
> a
> écrit :
>
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 3.21.4, a new patch release
> > with 9 improvements and fixes.
> >
> > Release notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12354021=12311211
> >
> > == Apache Camel 3.21.4 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1669/
> >
> > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1669/org/apache/camel/apache-camel/3.21.4/
> >
> > Tag: https://github.com/apache/camel/releases/tag/camel-3.21.4
> >
> > == Apache Camel Spring Boot 3.21.4 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1670/
> >
> > Tag:
> >
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.21.4
> >
> > == Apache Camel Karaf 3.21.4 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1671/
> >
> > Tag:
> https://github.com/apache/camel-karaf/releases/tag/camel-karaf-3.21.4
> >
> > Please test this release candidate and cast your vote:
> > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > Karaf 3.21.4
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Should *IT tests be run with failsafe instead of surefire?

[Otavio Rodolfo Piske]

Hi,

Yes, the integration tests (*IT.java) should be running with the failsafe
plugin.

Which ones are these? If you would like to submit a PR or provide a few of
those, I can take a look (opening a ticket is OK too).

Kind regards

On Wed, Jan 24, 2024 at 9:22 PM Craig Ziesman  wrote:

> I've been working with the Camel build and investigating test failures.
>
> There are many tests that use TestContainers and Docker in *IT.java classes
> that are currently being run by the surefire plugin. In my opinion, these
> tests ought to be run by failsafe, as they seem to meet the definition of
> integration tests, not unit tests, and should not cause the whole build to
> fail if any of them fail.
>
> I would be happy to generate a PR to move these tests to surefire if there
> is no objection from the team.
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Apache Camel 4.4 LTS release in February 2024

[Otavio Rodolfo Piske]

+1 from me.

I have a few more things to do for the Clock API and that's it on my end.

Kind regards

On Wed, Jan 3, 2024 at 10:25 AM Claus Ibsen  wrote:

> Hi
>
> The next LTS release is 4.4 that is planned for February 2024.
>
> For this release we have the usual bunch of dependency upgrades.
> The next Spring Boot 3.2.x release (later this month).
> And the Quarkus team is also waiting for a new Quarkus release to upgrade.
>
> I have some more work on the new variable stuff to complete.
> But I will be on PTO for 2 full weeks and will not be online, leaving
> tomorrow.
>
> The JIRA has some items listed. Fell free to move to 4.5 if there are
> tickets that you know we wont have time to implement or look at.
>
> And our CI server and tests are looking good. We have a very low number of
> test failures, but would be good to keep it low and get green builds more
> often.
>
> There is 1 test that keeps failing on Java 21 (there is a ticket about it).
>
>
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Camel K 2.2.0 release *second attempt

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Pasquale!

On Wed, Jan 3, 2024 at 2:17 PM Gaëlle Fournier <
gaelle.fournier.w...@gmail.com> wrote:

> +1 (non-binding)
>
> Thanks Pasquale!
>
> ---
> Gaëlle
>
> Le mer. 3 janv. 2024 à 10:43, Pasquale Congiusti <
> pasquale.congiu...@gmail.com> a écrit :
>
> > Hello,
> >
> > This is a vote to release Apache Camel K 2.2.0. This release provides new
> > features [1] and sets the default runtime to Camel Quarkus 3.2.3 (based
> on
> > Camel 4.0.3).
> >
> > * A previous release attempt was canceled on December 22nd 2023 due to
> the
> > fact that it was based on a non LTS Camel version.
> >
> > Camel K release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k/2.2.0/
> >
> > Camel K Tag:
> > https://github.com/apache/camel-k/releases/tag/v2.2.0
> >
> > Camel K CRD Java dependency staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1666/
> >
> > Staging container image repository:
> > AMD64 architecture:
> >
> >
> https://hub.docker.com/layers/camelk/camel-k/2.2.0/images/sha256-60a3041d3c3be07e840926981b44cd0e883460534e0d9e74fdc0fdce38d6166e?context=explore
> > ARM64
> > <
> https://hub.docker.com/layers/camelk/camel-k/2.2.0/images/sha256-60a3041d3c3be07e840926981b44cd0e883460534e0d9e74fdc0fdce38d6166e?context=exploreARM64
> >
> > architecture (preview only):
> >
> >
> https://hub.docker.com/layers/camelk/camel-k/2.2.0-arm64/images/sha256-6d5d78e804dff04b61ca271c8aa192a9a53ebf2e26e801d0eca1bb45c5abde98?context=explore
> >
> > It's possible to install all staging artifacts with a single command
> > (preferably using the kamel CLI you find in Camel K release files):
> >
> > kamel install --operator-image=camelk/camel-k:2.2.0 --olm=false
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release Apache Camel K 2.2.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > I start the vote with my +1.
> >
> > Thanks and regards,
> > Pasquale Congiusti
> >
> > [1] https://github.com/apache/camel-k/milestone/47?closed=1
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Camel K Runtime 3.6.0 and 3.2.3

[Otavio Rodolfo Piske]

+1 (binding)

Thanks!

On Wed, Dec 13, 2023 at 5:06 AM Christoph Deppisch
 wrote:

> +1 (non-binding)
>
> Thank you Pasquale!
>
> Pasquale Congiusti  schrieb am Mo., 11. Dez.
> 2023, 16:13:
>
> > Hello,
> >
> > This is a combined vote to release Camel K Runtime 3.6.0 and 3.2.3. This
> > release will provide the runtime for to Camel Quarkus 3.6.0 (based on
> Camel
> > 4.2.0) and 3.2.3 respectively.
> >
> > # Camel K runtime version 3.2.3
> >
> > Camel K Runtime source files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/3.2.3/
> >
> > Camel K Runtime staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1656
> >
> > Camel K Runtime Tag:
> >
> >
> https://github.com/apache/camel-k-runtime/releases/tag/camel-k-runtime-project-3.2.3
> >
> > It's possible test the staging artifacts by installing the latest Camel K
> > CLI (kamel) with the staging repository and run any Integration with the
> > new runtime:
> >
> > -
> > kamel install --maven-repository=
> > https://repository.apache.org/content/repositories/orgapachecamel-1656
> > ...
> >
> > kamel run Test.java -t camel.runtime-version=3.2.3
> > -
> >
> > Please test these release candidates and cast your vote.
> >
> > # Camel K runtime version 3.6.0
> >
> > Camel K Runtime source files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k-runtime/3.6.0/
> >
> > Camel K Runtime staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1657
> >
> > Camel K Runtime Tag:
> >
> >
> https://github.com/apache/camel-k-runtime/releases/tag/camel-k-runtime-project-3.6.0
> >
> > It's possible test the staging artifacts by installing the latest Camel K
> > CLI (kamel) with the staging repository and run any Integration with the
> > new runtime:
> >
> > -
> > kamel install --maven-repository=
> > https://repository.apache.org/content/repositories/orgapachecamel-1657
> > ...
> >
> > kamel run Test.java -t camel.runtime-version=3.6.0
> > -
> >
> > Please test these release candidates and cast your vote.
> >
> > [ ] +1 Release Apache Camel K Runtime 3.6.0 and 3.2.3
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > I start the vote with my +1.
> >
> > Thanks and regards,
> > Pasquale Congiusti
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel 4.3.0

[Otavio Rodolfo Piske]

+1 (binding)

Tested on my own CI

Thanks!

On Tue, Dec 12, 2023 at 1:04 PM Nicolas Filotto
 wrote:

> Wonderful! I can see the log message "The type of thread detected is
> VIRTUAL" at startup
> +1 (binding)
>
> Thank you very much, Gregor
> Nicolas
> 
> De : Gregor Zurowski 
> Envoyé : mardi 12 décembre 2023 09:23
> À : dev@camel.apache.org 
> Objet : [VOTE] Release Apache Camel 4.3.0
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
>
> Hi Everyone:
>
> This is a vote to release Apache Camel 4.3.0, a new release with 108
> new features and improvements. It is the first Camel release that was
> built with Java 21.
>
> Release notes:
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fsecure%2FReleaseNote.jspa%3Fversion%3D12353751%26projectId%3D12311211=05%7C02%7CNicolas.Filotto%40qlik.com%7C98c5f25251e3484801a208dbfaec06f6%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638379663866118983%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=WS5TLwAEoNBvxybAcGzEvhJHW8V2IKckqvdgVIuBZcw%3D=0
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353751=12311211
> >
>
> == Apache Camel 4.3.0 ==
>
> Staging repository:
>
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachecamel-1658%2F=05%7C02%7CNicolas.Filotto%40qlik.com%7C98c5f25251e3484801a208dbfaec06f6%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638379663866118983%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=x0Atl%2B9JwOEkyQZRcSzqwlQxs7nIVPyokw4Qz7Py7go%3D=0
> 
>
> Tarballs:
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachecamel-1658%2Forg%2Fapache%2Fcamel%2Fapache-camel%2F4.3.0%2F=05%7C02%7CNicolas.Filotto%40qlik.com%7C98c5f25251e3484801a208dbfaec06f6%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638379663866118983%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=AkD%2FdT4w3u6UV7%2Fz5k1sqAYwlFNkGja%2FyzOeZ3iC99w%3D=0
> <
> https://repository.apache.org/content/repositories/orgapachecamel-1658/org/apache/camel/apache-camel/4.3.0/
> >
>
> Tag:
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fcamel%2Freleases%2Ftag%2Fcamel-4.3.0=05%7C02%7CNicolas.Filotto%40qlik.com%7C98c5f25251e3484801a208dbfaec06f6%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638379663866118983%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=USrKr2KhJlqBIuMjDtQtugze8FXz%2FaF1H4KbtnhLKJ4%3D=0
> 
>
> == Apache Camel Spring Boot 4.3.0 ==
>
> Staging repository:
>
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachecamel-1659%2F=05%7C02%7CNicolas.Filotto%40qlik.com%7C98c5f25251e3484801a208dbfaec06f6%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638379663866118983%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=hulI6A2h4%2FJVCN0NoeFxn20v%2FQxIWLbnIrzRy0WdG78%3D=0
> 
>
> Tag:
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fcamel-spring-boot%2Freleases%2Ftag%2Fcamel-spring-boot-4.3.0=05%7C02%7CNicolas.Filotto%40qlik.com%7C98c5f25251e3484801a208dbfaec06f6%7Cc21eeb5ff5a644e8a997124f2f7a497c%7C0%7C0%7C638379663866118983%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=jL9Yk%2BYlGPBKm%2BSdiOLnFyGLtwv7kY%2FuPw%2BQfDveDzw%3D=0
> <
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.3.0
> >
>
> Please test this release candidate and cast your vote:
> [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.3.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>
> The information transmitted is intended only for the person or entity to
> which it is addressed and may contain confidential and/or privileged
> material. Any review, retransmission, dissemination or other use of, or
> taking of any action in reliance upon, this information by persons or
> entities other than the intended recipient is prohibited. If you received
> this in error, please contact the sender and delete the material from any
> computer. Our Privacy & Cookie Notice<
> https://www.qlik.com/us/legal/privacy-and-cookie-notice> describes how we
> handle personal information.
> 

Re: [VOTE] Release Apache Camel Quarkus 3.6.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks James!

On Fri, Nov 24, 2023 at 12:46 PM Alexandre Gallice 
wrote:

> +1 (binding)
>
> Well done James,
> Alex
>
> On Fri, Nov 24, 2023 at 11:36 AM Claudio Miranda 
> wrote:
>
> > Em sex., 24 de nov. de 2023 às 09:05, James Netherton
> >  escreveu:
> > >
> > > This is a vote to release Apache Camel Quarkus 3.6.0.
> >
> > +1 non binding
> >
> > --
> >   Claudio Miranda
> >
> > clau...@claudius.com.br
> > http://www.claudius.com.br
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel Kamelets 4.2.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Andrea!

On Thu, Nov 16, 2023 at 12:07 PM Claus Ibsen  wrote:

> +1 (binding)
>
> On Thu, Nov 16, 2023 at 10:28 AM Andrea Cosentino 
> wrote:
>
> > Hello all,
> >
> > This is a vote for releasing camel-kamelets 4.2.0
> >
> > This release will support the 4.2.0 release of Apache Camel.
> >
> > This release also:
> > - Removed the kebab-case syntax for YAML DSL in Kamelets, by moving to
> > camelCase
> > - Removed some of the datatypes from the utils to the main Camel release
> > - Introduce some Kamelets for dealing with Kafka Schema Registries from
> > Azure and Apicurio
> >
> > More info at:
> > https://github.com/apache/camel-kamelets/blob/main/CHANGELOG.md
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.2.0
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1646
> > Kamelets Tag:
> > https://github.com/apache/camel-kamelets/releases/tag/v4.2.0
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 4.2.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
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel 4.0.3

[Otavio Rodolfo Piske]

+1 (binding)

Tested on my own CI.

Thanks Gregor!

On Wed, Nov 15, 2023 at 7:41 AM Gregor Zurowski 
wrote:

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


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel 4.2.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks!!!

On Mon, Nov 13, 2023 at 9:16 AM Alexandre Gallice 
wrote:

> +1 (binding)
>
> Well done Cameleers,
> Alex
>
> On Sun, Nov 12, 2023 at 7:53 PM Claudio Miranda 
> wrote:
>
> > +1 non binding
> >
> > Em sáb., 11 de nov. de 2023 às 13:01, Gregor Zurowski
> >  escreveu:
> > >
> > > Hi Everyone:
> > >
> > > This is a vote to release Apache Camel 4.2.0, a new release with 115
> > > fixes and improvements.
> > >
> > > Release notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353662=12311211
> > >
> > > == Apache Camel 4.2.0 ==
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1642/
> > >
> > > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1642/org/apache/camel/apache-camel/4.2.0/
> > >
> > > Tag: https://github.com/apache/camel/releases/tag/camel-4.2.0
> > >
> > > == Apache Camel Spring Boot 4.2.0 ==
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1643/
> > >
> > > Tag:
> >
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.2.0
> > >
> > > Please test this release candidate and cast your vote:
> > > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.2.0
> > > [ ] -1 Veto the release (provide specific comments)
> > >
> > > The vote is open for at least 72 hours.
> > >
> > > Thanks,
> > > Gregor
> >
> >
> >
> > --
> >   Claudio Miranda
> >
> > clau...@claudius.com.br
> > http://www.claudius.com.br
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Apache Camel 4.2.0 release with Java 21 support

[Otavio Rodolfo Piske]

I think they can be skipped using -Dskip.camel.maven.plugin.tests=true.

Kind regards

On Fri, Nov 10, 2023 at 2:05 PM Andrea Cosentino  wrote:

> Yes it is
>
> Il ven 10 nov 2023, 13:36 Gregor Zurowski  ha
> scritto:
>
> > I've also ran into the following error in the prepare phase:
> >
> > ```
> > [INFO] [WARNING] The requested profile "release" could not be
> > activated because it does not exist.
> > [INFO] [ERROR] Plugin
> > org.apache.camel:camel-package-maven-plugin:4.2.0-SNAPSHOT or one of
> > its dependencies could not be resolved: The following artifacts could
> > not be resolved:
> > org.apache.camel:camel-package-maven-plugin:jar:4.2.0-SNAPSHOT
> > (absent): Could not find artifact
> > org.apache.camel:camel-package-maven-plugin:jar:4.2.0-SNAPSHOT ->
> > [Help 1]
> > ```
> >
> > We've seen the same issue with the 4.1 release. Is it OK to disable
> > the integration tests for camel-package-maven-plugin?
> >
> > Thanks,
> > Gregor
> >
> > On Fri, Nov 10, 2023 at 1:34 PM Gregor Zurowski
> >  wrote:
> > >
> > > Hi Everyone,
> > >
> > > I've started with the release and already pushed the branches
> > > `camel-4.2.x` and `camel-spring-boot-4.2.x`. You can proceed and
> > > commit to the `main` branch.
> > >
> > > Thanks,
> > > Gregor
> > >
> > > On Fri, Nov 10, 2023 at 11:46 AM Claus Ibsen 
> > wrote:
> > > >
> > > > Hi Gregor
> > > >
> > > > Okay so the branches are ready for cutting Camel 4.2.0 release - good
> > luck.
> > > >
> > > >
> > > >
> > > >
> > > > On Mon, Nov 6, 2023 at 1:06 PM Gregor Zurowski <
> > gre...@list.zurowski.org>
> > > > wrote:
> > > >
> > > > > Sounds good to me.
> > > > >
> > > > > On Mon, Nov 6, 2023 at 9:24 AM Claus Ibsen 
> > wrote:
> > > > > >
> > > > > > Hi
> > > > > >
> > > > > > Can we aim for friday or the weekend or start of next week.
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Mon, Nov 6, 2023 at 7:56 AM Gregor Zurowski <
> > gre...@list.zurowski.org
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > As we are through with all patch releases, when should we aim
> for
> > > > > 4.2.0?
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Gregor
> > > > > > >
> > > > > > > On Mon, Oct 23, 2023 at 11:52 AM Claus Ibsen <
> > claus.ib...@gmail.com>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > Hi
> > > > > > > >
> > > > > > > > The big goal for 4.2.0 release is official Java 21 support
> > (runtime).
> > > > > > > >
> > > > > > > > The CI server is passing all expected tests. Only
> camel-ignite
> > does
> > > > > not
> > > > > > > > support Java 21, and this is on the way with a new Ignite
> > release
> > > > > later
> > > > > > > > this year.
> > > > > > > >
> > > > > > > > So after all the patch releases, then after that it would be
> > good to
> > > > > get
> > > > > > > > 4.2.0, so end users can use this with Java 21 and also
> provide
> > > > > feedback
> > > > > > > > before the next LTS end of year / January 2024.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Claus Ibsen
> > > > > > > > -
> > > > > > > > @davsclaus
> > > > > > > > Camel in Action 2: https://www.manning.com/ibsen2
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Claus Ibsen
> > > > > > -
> > > > > > @davsclaus
> > > > > > Camel in Action 2: https://www.manning.com/ibsen2
> > > > >
> > > >
> > > >
> > > > --
> > > > Claus Ibsen
> > > > -
> > > > @davsclaus
> > > > Camel in Action 2: https://www.manning.com/ibsen2
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Concurrency bug in DefaultProducerCache leads to wrong ProducerTemplates being returned in the acquireProducer method

[Otavio Rodolfo Piske]

Hi, I am interested in investigating this.

Please, can you create a ticket [1] on our Jira and attach the reproducer?

1.
https://camel.apache.org/camel-core/contributing/#_reporting_a_bug_or_problem

Kind regards

On Fri, Nov 10, 2023 at 3:50 PM Peter Nowak 
wrote:

> Hi all,
>
> i stumbled across a maybe critical concurrency bug in the
> DefaultProducerCache of camel 4.x under high (concurrent) load related
> to the change from this ticket
> https://issues.apache.org/jira/browse/CAMEL-19058 and this commit
>
> https://github.com/apache/camel/commit/921ce519331ac5c8b0a1dfd099f9acbaba4feeab
>
> We encountered strange misrouted exchanges (and therefor errors) after
> upgrading to camel 4.0 under high load scenarios - wrong producer
> templates were picked from the cache due to the lack of
> synchronization
>
> I have created a small unit test which show the problem (i placed it
> in the "DefaultProducerCacheTest" class - just a proof of concept, not
> cleaned up at all :D)
> ---
>
> @Test
> public void testAcquireConcurrencyIssues() throws
> InterruptedException, ExecutionException {
> DefaultProducerCache cache = new DefaultProducerCache(this, context,
> 0);
> cache.start();
> List endpoints = new ArrayList<>();
> for (int i = 0; i < 3; i++) {
> Endpoint e = context.getEndpoint("direct:queue:" + i);
> AsyncProducer p = cache.acquireProducer(e);
> endpoints.add(e);
> }
>
> assertEquals(3, cache.size());
>
> ExecutorService ex = Executors.newFixedThreadPool(16);
>
> List> callables = new ArrayList<>();
>
> for(int i = 0; i < 500; i++) {
> int index = i % 3;
> callables.add(() -> {
> Producer producer =
> cache.acquireProducer(endpoints.get(index));
> boolean isEqual =
>
> producer.getEndpoint().getEndpointUri().equalsIgnoreCase(endpoints.get(index).getEndpointUri());
>
> if(!isEqual) {
> System.out.println("Endpoint uri to acquire: " +
> endpoints.get(index).getEndpointUri() + ", returned producer (uri): "
> + producer.getEndpoint().getEndpointUri());
> }
>
> return isEqual;
> });
> }
>
> for (int i = 0; i < 100; i++) {
> System.out.println("Iteration: " + (i + 1));
> List> results = ex.invokeAll(callables);
> for (Future future : results) {
> assertEquals(true, future.get());
> }
> }
> }
> ---
>
> Fails on my machine 10 out of 10
>
> if i synchronize the read (also just ugly for testing purposes, no
> performance testing done) in the "acquire" method in the
> "DefaultProducerCache" the test is green every time:
>
> Changes in the "DefaultProducerCache":
> -
>
> @Override
> public AsyncProducer acquireProducer(Endpoint endpoint) {
> // Try to favor thread locality as some data in the producer's
> cache may be shared among threads,
> // triggering cases of false sharing
> synchronized (this) {
> if (endpoint == lastUsedEndpoint &&
> endpoint.isSingletonProducer()) {
> return lastUsedProducer;
> }
> }
>
> try {
> AsyncProducer producer = producers.acquire(endpoint);
> if (statistics != null) {
> statistics.onHit(endpoint.getEndpointUri());
> }
>
> synchronized (this) {
> lastUsedEndpoint = endpoint;
> lastUsedProducer = producer;
> }
>
> return producer;
> } catch (Exception e) {
> throw new FailedToCreateProducerException(endpoint, e);
> }
> }
> -
>
> With the current approach of just syncing the write to the variables
> lastUsedEndpoint/Producer, still other threads can read the variables
> in between and then get a wrong producer template returned not
> matching to the requested endpoint.
>
> Best regards,
> Peter Nowak
>
> --
> Peter Nowak
> peter.no...@ecosio.com
> ecosio GmbH
> Lange Gasse 30 | 1080 Wien | Austria
> VAT number: ATU68241501, FN 405017p, Commercial Court Vienna
> Managing Directors: Christoph Ebm, Philipp Liegl, Marco Zapletal
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Apache Camel 4.2.0 release with Java 21 support

[Otavio Rodolfo Piske]

Hi, I don't have anything big on my side. There is an ongoing contribution
from a user that fixes quite a few of the Kafka issues related to
breakOnFirstError, but there won't be time to finish it before release.
This will have to be backported later on.

Kind regards


On Fri, Nov 10, 2023 at 9:58 AM Andrea Cosentino  wrote:

> All good from my side.
>
> Il giorno gio 9 nov 2023 alle ore 15:12 Andrea Cosentino <
> anco...@gmail.com>
> ha scritto:
>
> > There is nothing from my side. I'd like to update the description for AWS
> > components, but this could be completed in 4.3.0.
> >
> > I'll do a quick check tomorrow to see if there are new CVEs we could fix
> > easily.
> >
> > Il giorno gio 9 nov 2023 alle ore 15:10 Claus Ibsen <
> claus.ib...@gmail.com>
> > ha scritto:
> >
> >> Hi
> >>
> >> Just a heads up that we want to get ready for the 4.2 release.
> >>
> >> There is this big PR that Steve needs to quickly resolve and get in
> shape
> >> for merging, or it risk being postponed to 4.3 release.
> >> https://github.com/apache/camel/pull/11906
> >>
> >>
> >>
> >>
> >>
> >> On Mon, Nov 6, 2023 at 1:06 PM Gregor Zurowski <
> gre...@list.zurowski.org>
> >> wrote:
> >>
> >> > Sounds good to me.
> >> >
> >> > On Mon, Nov 6, 2023 at 9:24 AM Claus Ibsen 
> >> wrote:
> >> > >
> >> > > Hi
> >> > >
> >> > > Can we aim for friday or the weekend or start of next week.
> >> > >
> >> > >
> >> > >
> >> > > On Mon, Nov 6, 2023 at 7:56 AM Gregor Zurowski <
> >> gre...@list.zurowski.org
> >> > >
> >> > > wrote:
> >> > >
> >> > > > As we are through with all patch releases, when should we aim for
> >> > 4.2.0?
> >> > > >
> >> > > > Thanks,
> >> > > > Gregor
> >> > > >
> >> > > > On Mon, Oct 23, 2023 at 11:52 AM Claus Ibsen <
> claus.ib...@gmail.com
> >> >
> >> > > > wrote:
> >> > > > >
> >> > > > > Hi
> >> > > > >
> >> > > > > The big goal for 4.2.0 release is official Java 21 support
> >> (runtime).
> >> > > > >
> >> > > > > The CI server is passing all expected tests. Only camel-ignite
> >> does
> >> > not
> >> > > > > support Java 21, and this is on the way with a new Ignite
> release
> >> > later
> >> > > > > this year.
> >> > > > >
> >> > > > > So after all the patch releases, then after that it would be
> good
> >> to
> >> > get
> >> > > > > 4.2.0, so end users can use this with Java 21 and also provide
> >> > feedback
> >> > > > > before the next LTS end of year / January 2024.
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > > --
> >> > > > > Claus Ibsen
> >> > > > > -
> >> > > > > @davsclaus
> >> > > > > Camel in Action 2: https://www.manning.com/ibsen2
> >> > > >
> >> > >
> >> > >
> >> > > --
> >> > > Claus Ibsen
> >> > > -
> >> > > @davsclaus
> >> > > Camel in Action 2: https://www.manning.com/ibsen2
> >> >
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -
> >> @davsclaus
> >> Camel in Action 2: https://www.manning.com/ibsen2
> >>
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel Quarkus 3.2.2

[Otavio Rodolfo Piske]

I apologize. I missed the fact that the voting had been closed.

On Tue, Nov 7, 2023 at 11:24 AM Otavio Rodolfo Piske 
wrote:

> +1 (binding)
>
> Thanks!
>
> On Mon, Nov 6, 2023 at 1:31 PM James Netherton 
> wrote:
>
>> +1 (binding)
>>
>> On Fri, 3 Nov 2023 at 12:27, James Netherton 
>> wrote:
>>
>> > Hi,
>> >
>> > This is a vote to release Apache Camel Quarkus 3.2.2.
>> >
>> > Highlights:
>> >
>> > * Camel 4.0.2
>> > * Quarkus 3.2.7.Final
>> >
>> > All commits:
>> >
>> > https://github.com/apache/camel-quarkus/compare/3.2.1...3.2.2
>> >
>> > Staging repository:
>> >
>> > <http://goog_339624509>
>> > https://repository.apache.org/content/repositories/orgapachecamel-1638
>> >
>> > Tag:
>> >
>> > https://github.com/apache/camel-quarkus/releases/tag/3.2.2
>> >
>> > Source release package:
>> >
>> >
>> >
>> https://repository.apache.org/service/local/repositories/orgapachecamel-1638/content/org/apache/camel/quarkus/camel-quarkus/3.2.2/camel-quarkus-3.2.2-src.zip
>> >
>> > Please test this release candidate and cast your vote.
>> >
>> > [ ] +1 Release the binaries as Apache Camel Quarkus 3.2.2
>> > [ ] -1 Veto the release (provide specific comments)
>> >
>> > The vote is open for at least 72 hours.
>> >
>>
>
>
> --
> Otavio R. Piske
> http://orpiske.net
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel Quarkus 3.2.2

[Otavio Rodolfo Piske]

+1 (binding)

Thanks!

On Mon, Nov 6, 2023 at 1:31 PM James Netherton 
wrote:

> +1 (binding)
>
> On Fri, 3 Nov 2023 at 12:27, James Netherton 
> wrote:
>
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 3.2.2.
> >
> > Highlights:
> >
> > * Camel 4.0.2
> > * Quarkus 3.2.7.Final
> >
> > All commits:
> >
> > https://github.com/apache/camel-quarkus/compare/3.2.1...3.2.2
> >
> > Staging repository:
> >
> > 
> > https://repository.apache.org/content/repositories/orgapachecamel-1638
> >
> > Tag:
> >
> > https://github.com/apache/camel-quarkus/releases/tag/3.2.2
> >
> > Source release package:
> >
> >
> >
> https://repository.apache.org/service/local/repositories/orgapachecamel-1638/content/org/apache/camel/quarkus/camel-quarkus/3.2.2/camel-quarkus-3.2.2-src.zip
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binaries as Apache Camel Quarkus 3.2.2
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
>


-- 
Otavio R. Piske
http://orpiske.net

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

[Otavio Rodolfo Piske]

+1 (binding)

Thanks!

On Tue, Oct 24, 2023 at 5:33 PM Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> Regards
> JB
>
> On Tue, Oct 24, 2023 at 12:06 PM Gregor Zurowski
>  wrote:
> >
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 3.21.2, a new patch release
> > with 11 improvements and fixes.
> >
> > Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353670=12311211
> >
> > == Apache Camel 3.21.2 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1630/
> >
> > Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1630/org/apache/camel/apache-camel/3.21.2/
> >
> > Tag: https://github.com/apache/camel/releases/tag/camel-3.21.2
> >
> > == Apache Camel Spring Boot 3.21.2 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1631/
> >
> > Tag:
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.21.2
> >
> > == Apache Camel Karaf 3.21.2 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1632/
> >
> > Tag:
> https://github.com/apache/camel-karaf/releases/tag/camel-karaf-3.21.2
> >
> > Please test this release candidate and cast your vote:
> > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > Karaf 3.21.2
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Apache Camel 4.2.0 release with Java 21 support

[Otavio Rodolfo Piske]

Hi,

I am working on something I hope we can include in 4.2.0, but it's no big
deal if I don't finish in time.

So, from me, +1

Thanks!!!


On Mon, Oct 23, 2023 at 11:55 AM Andrea Cosentino  wrote:

> Big +1.
>
> Thanks for bring this up to the community.
>
> Il giorno lun 23 ott 2023 alle ore 11:52 Claus Ibsen <
> claus.ib...@gmail.com>
> ha scritto:
>
> > Hi
> >
> > The big goal for 4.2.0 release is official Java 21 support (runtime).
> >
> > The CI server is passing all expected tests. Only camel-ignite does not
> > support Java 21, and this is on the way with a new Ignite release later
> > this year.
> >
> > So after all the patch releases, then after that it would be good to get
> > 4.2.0, so end users can use this with Java 21 and also provide feedback
> > before the next LTS end of year / January 2024.
> >
> >
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel 4.0.2

[Otavio Rodolfo Piske]

+1 (binding)

Thanks!

On Mon, Oct 23, 2023 at 11:25 AM Claus Ibsen  wrote:

> +1 (binding)
>
> On Mon, Oct 23, 2023 at 10:45 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
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel Kamelets 4.1.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Andrea!

On Mon, Oct 23, 2023 at 10:52 AM Claus Ibsen  wrote:

> +1 (binding)
>
> On Mon, Oct 23, 2023 at 10:50 AM Andrea Cosentino 
> wrote:
>
> > Hello all,
> >
> > This is a vote for releasing camel-kamelets 4.1.0
> >
> > This release will support the 4.1.0 release of Apache Camel.
> >
> > Kamelets release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.1.0
> > Kamelets staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1629
> > Kamelets Tag:
> > https://github.com/apache/camel-kamelets/releases/tag/v4.1.0
> >
> > Please cast your vote.
> >
> > [ ] +1 Release camel-kamelets 4.1.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
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel K 2.1.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Pasquale!

On Wed, Oct 18, 2023 at 3:23 PM Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> Regards
> JB
>
> On Mon, Oct 16, 2023 at 6:31 PM Pasquale Congiusti
>  wrote:
> >
> > Hello,
> >
> > This is a vote to release Apache Camel K 2.1.0. This release provides
> many
> > new features [1] and set the default runtime to Camel Quarkus 3.2.0
> (based
> > on Camel 4).
> >
> > Camel K release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k/2.1.0/
> >
> > Camel K Tag:
> > https://github.com/apache/camel-k/releases/tag/v2.1.0
> >
> > Camel K CRD Java dependency staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1625/
> >
> > Staging container image repository:
> > AMD64 architecture:
> >
> https://hub.docker.com/layers/camelk/camel-k/2.1.0/images/sha256-58444fc7331bf2d8f6d7dbe8ba47c7a4770654f82ca11eac25b468d26a166d1a?context=explore
> > ARM64 architecture (preview only):
> >
> https://hub.docker.com/layers/camelk/camel-k/2.1.0-arm64/images/sha256-537e0c45714d5b10433f3aca8775bd3d3db38efc3da80f0255291a9c093f5e68?context=explore
> >
> > It's possible to install all staging artifacts with a single command
> > (preferably using the kamel CLI you find in Camel K release files):
> >
> > kamel install --operator-image=camelk/camel-k:2.1.0 --olm=false
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release Apache Camel K 2.1.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > I start the vote with my +1.
> >
> > Thanks and regards,
> > Pasquale Congiusti
> >
> > [1] https://github.com/apache/camel-k/milestone/45?closed=1
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel Quarkus 3.5.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks James!

On Fri, Oct 20, 2023 at 9:41 AM James Netherton 
wrote:

> Hi,
>
> This is a vote to release Apache Camel Quarkus 3.5.0.
>
> Highlights:
>
> * Camel 4.1.0
> * Quarkus 3.5.0
>
> All commits:
>
> https://github.com/apache/camel-quarkus/compare/3.4.0...3.5.0
>
> Staging repository:
>
> 
> https://repository.apache.org/content/repositories/orgapachecamel-1626
>
> Tag:
>
> https://github.com/apache/camel-quarkus/releases/tag/3.5.0
>
> Source release package:
>
>
> https://repository.apache.org/content/repositories/orgapachecamel-1626/org/apache/camel/quarkus/camel-quarkus/3.5.0/camel-quarkus-3.5.0-src.zip
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binaries as Apache Camel Quarkus 3.5.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>


-- 
Otavio R. Piske
http://orpiske.net

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

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Gregor!

On Wed, Sep 27, 2023 at 2:11 PM Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> Regards
> JB
>
> On Wed, Sep 27, 2023 at 9:52 AM Gregor Zurowski
>  wrote:
> >
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 3.20.7 (LTS), a patch release
> > with 56 fixes and improvements.
> >
> > Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353329=12311211
> >
> > == Apache Camel 3.20.7 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1618/
> >
> > Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1618/org/apache/camel/apache-camel/3.20.7/
> >
> > Tag: https://github.com/apache/camel/releases/tag/camel-3.20.7
> >
> > == Apache Camel Spring Boot 3.20.7 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1620/
> >
> > Tag:
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.20.7
> >
> > == Apache Camel Karaf 3.20.7 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1621/
> >
> > Tag:
> https://github.com/apache/camel-karaf/releases/tag/camel-karaf-3.20.7
> >
> > Please test this release candidate and cast your vote:
> > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > Karaf 3.20.7
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
>


-- 
Otavio R. Piske
http://orpiske.net

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

[Otavio Rodolfo Piske]

+1

Thanks Gregor!


On Mon, Sep 25, 2023 at 2:10 PM Alexandre Gallice 
wrote:

> +1 (binding)
>
> Nice cut Gregor,
> Alex
>
> On Mon, Sep 25, 2023 at 1:05 PM Babak Vahdat
>  wrote:
>
> > +1 (binding)
> >
> > Thanks Gregor!
> >
> > --
> > Babak
> >
> > > On 25 Sep 2023, at 12:15, Gregor Zurowski 
> > wrote:
> > >
> > > Hi Everyone:
> > >
> > > This is a vote to release Apache Camel 3.21.1, a new LTS release with
> > > 63 improvements and fixes.
> > >
> > > Release notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353345=12311211
> > >
> > > == Apache Camel 3.21.1 ==
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1613/
> > >
> > > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1613/org/apache/camel/apache-camel/3.21.1/
> > >
> > > Tag: https://github.com/apache/camel/releases/tag/camel-3.21.1
> > >
> > > == Apache Camel Spring Boot 3.21.1 ==
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1614/
> > >
> > > Tag:
> >
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.21.1
> > >
> > > == Apache Camel Karaf 3.21.1 ==
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1615/
> > >
> > > Tag:
> > https://github.com/apache/camel-karaf/releases/tag/camel-karaf-3.21.1
> > >
> > > Please test this release candidate and cast your vote:
> > > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > > Karaf 3.21.1
> > > [ ] -1 Veto the release (provide specific comments)
> > >
> > > The vote is open for at least 72 hours.
> > >
> > > Thanks,
> > > Gregor
> >
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Apache Camel 4.1 release in October

[Otavio Rodolfo Piske]

+1 from me. We also have the new type converter which would be good to have
more people using.

Thanks!

On Tue, Sep 26, 2023 at 9:09 AM Claus Ibsen  wrote:

> Hi
>
> Thanks Gregor. I think it would be best to do the release before your PTO.
> So let's see if we can cut the release after all the patch releases have
> been done.
>
>
> On Mon, Sep 25, 2023 at 6:19 PM Gregor Zurowski 
> wrote:
>
> > +1 for me. I won't be available between October 13 and October 20, but
> > can work on the release either before or after those dates.
> >
> >
> > On Sat, Sep 23, 2023 at 10:29 AM Claus Ibsen 
> > wrote:
> > >
> > > Hi
> > >
> > > I think it would be good to get 4.1 released after our patch releases.
> > >
> > > This will be a non LTS release but its good baseline for follow up
> > releases
> > > where we can work on adding support for Java 21 that is planned for the
> > > next LTS by end of this year/early January.
> > >
> > > We may need a 4.2 non LTS also, before we cut 4.3 as LTS. But let's see
> > > later what makes sense.
> > >
> > > Any thoughts?
> > >
> > > --
> > > Claus Ibsen
> > > -
> > > @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release of Apache Camel Karavan 4.0.0. 2nd attempt

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Marat!

On Mon, Sep 25, 2023 at 12:44 PM Zoran Regvart 
wrote:

> +1 (binding)
>
> Thanks Marat!
>
> On Fri, Sep 22, 2023 at 4:36 PM Marat Gubaidullin
>  wrote:
> >
> > Dear Camel Developers,
> >
> > This is a vote for the release of Apache Camel Karavan version 4.0.0.
> >
> > What's new in this version:
> >
> > 1. Expanded Platform Support: Karavan extends its compatibility to a
> wider
> > range of platforms, including:
> > - Docker (New!)
> > - Kubernetes
> > - Openshift
> >
> > How to run Karavan in different platforms:
> > https://github.com/apache/camel-karavan/blob/main/docs/README.md
> >
> > 2. Simplified Integrations build process:
> > Users can now customize integration container build via a shell script
> > conveniently stored in the same repository.
> >
> > 3. Project Topology view:
> > Karavan introduces a brand new project Topology view, offering a
> top-level
> > overview of integrations within your project.
> > This feature enhances your project's visibility and makes it easier to
> > manage your integrations effectively.
> >
> > 4. Pure Camel:
> > We are using camel-main (also known as standalone) runtime in this
> release.
> >
> > 5. Version Updates: We have updated the following components to their
> > latest versions:
> > - Camel 4.0.0
> > - Kamelets 4.0.0
> > - Jkube 1.14.0
> >
> > Source release package:
> > https://dist.apache.org/repos/dist/dev/camel/camel-karavan/4.0.0/
> >
> > Some files in the codebase have missing licence headers still. This is
> done
> > intentionally, because these files are code snippets/templates used to
> > generate user's code.
> >
> > VS Code Extension
> > https://github.com/apache/camel-karavan/releases/tag/4.0.0
> >
> > We encourage all Camel contributors to participate in this release vote.
> > Your feedback and contributions play a crucial role in making Apache
> Camel
> > Karavan better with each release.
> >
> > Please cast your vote by replying to this email with your decision:
> > [ ] +1 Release
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The voting period will remain open for 72 hours.
> >
> > Thank you for your continued support and dedication to the Apache Camel
> > project.
> >
> > My +1 is here
> >
> > Have a nice day,
> > Marat
>
>
>
> --
> Zoran Regvart
>


-- 
Otavio R. Piske
http://orpiske.net

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

[Otavio Rodolfo Piske]

+1 (binding)

Thanks!

On Thu, Sep 21, 2023 at 3:36 PM Zineb Bendhiba 
wrote:

> +1 (binding)
>
> Le jeu. 21 sept. 2023 à 13:30, Andrea  a écrit :
>
> > Hello all,
> >
> > This is a vote to release Apache Camel-kafka-connector 4.0.0
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1610
> >
> > Tag:
> >
> >
> https://gitbox.apache.org/repos/asf?p=camel-kafka-connector.git;a=tag;h=refs/tags/camel-kafka-connector-4.0.0
> >
> > Updated to camel 4
> >
> > Please test this release candidate and cast your vote.
> > [ ] +1 Release the binary as  Apache Camel-kafka-connector 4.0.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Andrea.
> >
>
>
> --
> Zineb Bendhiba
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Camel Quarkus 3.4.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Zineb!

On Fri, Sep 15, 2023 at 10:48 AM Alexandre Gallice 
wrote:

> +1 (binding)
>
> Looks good, well done everybody :)
> Alex
>
> On Fri, Sep 15, 2023 at 10:43 AM Zineb Bendhiba 
> wrote:
>
> > Hello,
> >
> >
> >
> > This is a vote to release Apache Camel Quarkus 3.4.0.
> >
> >
> >
> > Highlights:
> >
> >
> >
> > * Camel 4.0.0
> >
> >
> > * Quarkus 3.4.0
> >
> >
> >
> > Milestone:
> >
> > https://github.com/apache/camel-quarkus/milestone/47?closed=1
> >
> >
> > All commits:
> >
> > https://github.com/apache/camel-quarkus/compare/3.2.0...3.4.0
> >
> >
> >
> > Staging repository:
> >
> > https://repository.apache.org/content/repositories/orgapachecamel-1608/
> >
> >
> >
> > Tag:
> >
> > https://github.com/apache/camel-quarkus/releases/tag/3.4.0
> >
> >
> >
> > Source release package:
> >
> >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1608/org/apache/camel/quarkus/camel-quarkus/3.4.0/camel-quarkus-3.4.0-src.zip
> > <
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1608/org/apache/camel/quarkus/camel-quarkus/3.4.0/camel-quarkus-3.4.0-src.zip
> > >
> >
> >
> >
> > Please test this release candidate and cast your vote.
> >
> >
> >
> > [ ] +1 Release the binaries as Apache Camel Quarkus 3.4.0
> >
> >
> > [ ] -1 Veto the release (provide specific comments)
> >
> >
> >
> > The vote is open for at least 72 hours.
> >
> >
> > --
> >
> > Zineb Bendhiba
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Draft Camel Board Report for September 2023

[Otavio Rodolfo Piske]

Looks good to me as well.

Thanks Andrea!

On Tue, Sep 5, 2023 at 11:41 AM Nicolas Filotto  wrote:

> It looks good to me too, thanks Andrea
> 
> From: Jean-Baptiste Onofré 
> Sent: Tuesday, September 5, 2023 11:24
> To: dev@camel.apache.org 
> Subject: Re: Draft Camel Board Report for September 2023
>
> It looks good to me.
>
> Thanks !
> Regards
> JB
>
> On Tue, Sep 5, 2023 at 7:00 AM Andrea Cosentino  wrote:
> >
> > Hello all,
> >
> > I prepare the draft for September 2023, I'm planning to submit it
> tomorrow.
> > Feedback is welcome.
> >
> > ## Description:
> > The mission of Apache Camel is the creation and maintenance of an
> > open-source
> > integration framework based on known Enterprise Integration Patterns.
> >
> > ## Project Status:
> > Project status: Ongoing with high activity
> > Issues: There are no issues requiring board attention at this time.
> >
> > ## Membership Data:
> > Apache Camel was founded 2008-12-17 (15 years ago)
> > There are currently 88 committers and 44 PMC members in this project.
> > The Committer-to-PMC ratio is 2:1.
> >
> > Community changes, past quarter:
> > - No new PMC members. Last addition was Nicolas Filotto on 2023-04-05.
> > - Kengo Seki was added as committer on 2023-07-04
> >
> > ## Project Activity:
> > - We released Camel 3.14.9
> > - We released Camel 3.18.8
> > - We released Camel 3.20.6
> > - We released Camel 3.21.0
> > - We released Camel 4.0.0-RC1
> > - We released Camel 4.0.0
> > - Note: Camel releases have synchronized releases of Camel-Karaf and
> >   Camel-Spring-Boot too for 3.x, while for 4.x only Camel-Spring-Boot is
> >   synchronized.
> > - We released Camel 4.0.0, our main effort in the last 10 months.
> > - We are continuing release 3.18.x LTS release train and we are in the
> > process
> >   of releasing the next patch release.
> > - We started the release train for 3.20.x LTS, and we are already at the
> > sixth
> >   patch release. We want to release another patch release soon.
> > - We are still supporting Camel 3.14.x, an LTS train, but it's going EOL,
> >   there will be another release 3.14.10.
> > - We released another 3.x LTS Release the 3.21.0
> > - For Camel K we released a really important 2.0 release with a lot of
> good
> >   work from community.
> > - For Camel-Kamelets releases
> > - We released Camel Kameletes 3.20.6
> > - We released Camel Kameletes 3.21.0
> > - We released Camel Kamelets 4.0.0-RC1
> > - We are working hard on releasing version 4.0.0 too
> > - Camel-Kamelets is not only related to camel k anymore so it could be
> used
> >   with all the Camel's flavours
> > - The Camel-Quarkus work is going ahead following the main camel releases
> > with
> >   multiple releases
> > - We released Camel-quarkus 2.16.0
> > - We released Camel-quarkus 3.0.0-RC1
> > - We released Camel-quarkus 3.0.0-RC2
> > - We released Camel-quarkus 3.2.0
> > - Camel-Kameleon and Camel-Karavan are improving and more and more
> >   contributors are continuing to help. We are improving the projects by
> >   supporting new features and aligning with LTS releases 3.21.0 as in the
> > last
> >   report
> > - Camel Kafka Connector release based on Camel 3.20.6 has been released.
> > - Camel Kafka Connector release based on Camel 3.21.0 has been released.
> > - Work for supporting Camel 4.0.0 is going ahead
> > - Generally speaking we are working on supporting Camel 4 in all the
> > runtimes
> >   provided and this is taking a lot of effort.
> >
> >
> > ## Community Health:
> > - 296 issues opened on GitHub, past quarter (15% decrease) and 308 issues
> >   closed on GitHub, past quarter (5% decrease): Since we were working on
> >   releasing Camel 4.0.0 some of the subprojects using gh issues have seen
> > less
> >   focused work, Camel is using JIRA for tracking the work. We focused on
> > 4.0.0
> >   for a long time.
> > - 4992 commits in the past quarter (14% decrease) and 133 code
> contributors
> > in
> >   the past quarter (3% increase): The commits decrease is related to the
> > work
> >   done for Camel 4.0.0, at some point in the development we choose to
> slow
> >   down a bit. The camel core team was focusing on Camel 4.x. We saw
> sporadic
> >   contributions from new contributors in subprojects and main Camel.
> > - 1601 PRs opened on GitHub, past quarter (4% decrease) and 1602 PRs
> closed
> > on
> >   GitHub, past quarter (4% deccrease): on some of the subprojects the
> > activity
> >   was slowing down for stabilization reasons and for the focus on Camel
> > 4.0.0.
> > - dev@camel.apache.org had a 23% increase in traffic in the past quarter
> > (412
> >   emails compared to 334): There was a spike in the dev ML because of
> >   questions and discussions around the development and final decision for
> >   Camel 4.0.0
> > - iss...@camel.apache.org had a 56% increase in traffic in the past
> quarter
> >   (2964 emails compared to 1888): There was activity in JIRA mostly for
> > Camel
> >4 work and 

Re: [VOTE] Release Apache Camel K 2.0.1

[Otavio Rodolfo Piske]

+1 (binding)

Thanks!

On Wed, Aug 30, 2023 at 2:48 PM Claudio Miranda 
wrote:

> +1 non binding
>
> Em qua., 30 de ago. de 2023 às 07:51, Pasquale Congiusti
>  escreveu:
> >
> > This is a vote to release Apache Camel K 2.0.1. The release also contains
>
>
>
>
> --
>   Claudio Miranda
>
> clau...@claudius.com.br
> http://www.claudius.com.br
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Camel Quarkus 3.2.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Zineb!

On Tue, Aug 29, 2023 at 7:13 AM Andrea Cosentino  wrote:

> +1 (binding)
>
> Thanks Zineb
>
> Il lun 28 ago 2023, 22:17 Zineb Bendhiba  ha
> scritto:
>
> > Hello,
> >
> >
> > This is a vote to release Apache Camel Quarkus 3.2.0.
> >
> >
> > Highlights:
> >
> >
> > * Camel 4.0.0
> >
> > * Quarkus 3.2.5.Final
> >
> >
> > All commits:
> >
> >
> > https://github.com/apache/camel-quarkus/compare/3.0.0-RC2...3.2.0
> >
> >
> > Staging repository:
> >
> >
> > https://repository.apache.org/content/repositories/orgapachecamel-1601/
> >
> >
> > Tag:
> >
> >
> > https://github.com/apache/camel-quarkus/releases/tag/3.2.0
> >
> >
> > Source release package:
> >
> >
> >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1601/org/apache/camel/quarkus/camel-quarkus/3.2.0/camel-quarkus-3.2.0-src.zip
> >
> >
> > Please test this release candidate and cast your vote.
> >
> >
> > [ ] +1 Release the binaries as Apache Camel Quarkus 3.2.0
> >
> > [ ] -1 Veto the release (provide specific comments)
> >
> >
> > The vote is open for at least 72 hours.
> >
> > --
> > Zineb Bendhiba
> >
>


-- 
Otavio R. Piske
http://orpiske.net

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

[Otavio Rodolfo Piske]

+1 (binding)

Thanks!!!

On Sat, Aug 26, 2023 at 11:31 AM zineb bendhiba 
wrote:

> Hello
>
> +1 (binding)
>
> Thanks Andrea
>
> Zineb Bendhiba
>
> > Le 25 août 2023 à 12:08, Andrea  a écrit :
> >
> > Hello all,
> >
> > This is a vote to release Apache Camel-kafka-connector 3.21.0
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1600
> >
> > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel-kafka-connector.git;a=tag;h=refs/tags/camel-kafka-connector-3.21.0
> >
> > Updated to camel 3.21.0
> >
> > Please test this release candidate and cast your vote.
> > [ ] +1 Release the binary as  Apache Camel-kafka-connector 3.21.0
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Andrea.
>


-- 
Otavio R. Piske
http://orpiske.net

Re: GitHub discussions for Apache Camel project

[Otavio Rodolfo Piske]

Thanks Claus!

+1 for this. I think the moment is appropriate, as we have released Camel
4.0 and we can start using this for 4.1 discussions and beyond!


On Mon, Aug 14, 2023 at 3:43 PM Claus Ibsen  wrote:

> Hi
>
> We have talked about opening up for GH discussions at
> https://github.com/apache/camel
>
> This allows more community users to more easily get involved, and ask for
> help, and whatnot.
>
> Also for technical discussion, then instead of DEV mailing list, then its
> maybe easier on GH as we can more easily link to existing source code,
> projects when its technical.
>
> We would then need to setup GH discussions in a way so users can find space
> for support/help, and another space where we can have roadmap and
> design/tech discussions etc.
>
> For big organisational decisions and whatnot,
> then we should still use the DEV mailing list.
>
> Any thoughts?
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel 4.0.0

[Otavio Rodolfo Piske]

+1 (binding)

Tested on my own CI. Everything looks good.

Thanks Gregor!

Kind regards

On Fri, Aug 11, 2023 at 12:31 PM Babak Vahdat
 wrote:

> +1 (binding)
>
> Thanks Gregor!
> --
> Babak
>
> > Am 11.08.2023 um 11:56 schrieb James Netherton  >:
> >
> > +1 (binding)
> >
> > Thanks Gregor!
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Release Apache Camel 4.0 GA later this month

[Otavio Rodolfo Piske]

+1 from me

Thanks!


On Wed, Aug 2, 2023 at 9:54 AM Gregor Zurowski 
wrote:

> +1 works for me
>
> On Tue, Aug 1, 2023 at 10:42 AM Claus Ibsen  wrote:
> >
> > Hi
> >
> > We have just released RC2 to give community and others an easier
> > opportunity to test and try Camel 4, before we build the GA release.
> >
> > So if you have a chance to try RC2 then provide feedback as soon as
> > possible.
> >
> > We are currently focusing on core bug fixes, dependency upgrades, CVEs,
> and
> > CI test stability.
> >
> > I would like to propose that by wednesday 9th aug (afternoon) we should
> aim
> > to be ready, so Gregor can take time to build the release. And we need
> some
> > "room" in case the GA build needs a 2nd build.
> >
> > Any comments?
> >
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Camel Quarkus 3.0.0-RC2

[Otavio Rodolfo Piske]

+1 (binding)

Thanks!

On Mon, Jul 31, 2023 at 11:55 AM Alexandre Gallice 
wrote:

> +1 (binding)
>
> Well done James,
> Alex
>
> On Mon, Jul 31, 2023 at 9:38 AM Pasquale Congiusti <
> pasquale.congiu...@gmail.com> wrote:
>
> > +1 (binding)
> >
> > Thanks James!
> >
> > On Mon, Jul 31, 2023 at 7:45 AM Andrea Cosentino 
> > wrote:
> >
> > > +1 (binding)
> > >
> > > Thanks.
> > >
> > > Il giorno dom 30 lug 2023 alle ore 12:51 James Netherton <
> > > jamesnether...@gmail.com> ha scritto:
> > >
> > > > Hi,
> > > >
> > > > This is a vote to release Apache Camel Quarkus 3.0.0-RC2.
> > > >
> > > > Highlights:
> > > >
> > > > * Camel 4.0.0-RC2
> > > > * Quarkus 3.2.2.Final
> > > >
> > > > All commits:
> > > >
> > > >
> https://github.com/apache/camel-quarkus/compare/3.0.0-RC1...3.0.0-RC2
> > > >
> > > > Staging repository:
> > > >
> > > > 
> > > >
> https://repository.apache.org/content/repositories/orgapachecamel-1597
> > > >
> > > > Tag:
> > > >
> > > > https://github.com/apache/camel-quarkus/releases/tag/3.0.0-RC2
> > > >
> > > > Source release package:
> > > >
> > > >
> > > >
> > >
> >
> https://repository.apache.org/service/local/repositories/orgapachecamel-1597/content/org/apache/camel/quarkus/camel-quarkus/3.0.0-RC2/camel-quarkus-3.0.0-RC2-src.zip
> > > >
> > > > Please test this release candidate and cast your vote.
> > > >
> > > > [ ] +1 Release the binaries as Apache Camel Quarkus 3.0.0-RC2
> > > > [ ] -1 Veto the release (provide specific comments)
> > > >
> > > > The vote is open for at least 72 hours.
> > > >
> > >
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Using camel-test-infra-core vs regular testing

[Otavio Rodolfo Piske]

Hi Claus,

Thanks for the discussion and sharing your thoughts and concerns about this
feature with me!

On my side there also was a big miscommunication: I should have done a
better job engaging the community on the discussions about CAMEL-18957, and
what would be the short, medium and long term plans for it.

After we get Camel 4 GA released, I'll share an updated plan with more
details and also engage the community so that we can iteratively and
jointly design and implement this feature.

As for GitHub discussions: +1 for that idea. I think it can be a good venue
for discussions.

Kind regards

On Thu, Jul 27, 2023 at 10:23 AM Nicolas Filotto 
wrote:

> +1 to use GitHub Discussion too
> 
> From: Andrea Cosentino 
> Sent: Thursday, July 27, 2023 10:13
> To: dev 
> Subject: Re: Using camel-test-infra-core vs regular testing
>
> I'm +1 to use discussions and I think we could to enable it to INFRA.
>
> --
> Andrea Cosentino
> --
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Thursday, July 27, 2023 at 10:11:01 AM GMT+2, Claus Ibsen <
> claus.ib...@gmail.com> wrote:
>
>
>
>
>
> Hi
>
> I had a talk with Otabio about this subject.
>
> There has been some misunderstanding and miscommunication on my part, and
> this mail thread may also have a few related subjects conflated.
>
> In the short term we should focus on bringing Camel 4.0 to GA.
> After this release then I think there is time where we can focus on
> discussing this again, but from a fresh start.
> Otavio said he will at that given time put together some details and share
> it with the community.
>
>
>
> On another note we also wonder if we could try GitHub Discussion for this.
> As mailing lists are a bit out-of-date, and
> maybe GH discussions is a better place for a wider audience to see and
> bring feedback.
>
> The Camel Karavan project has GH discussions
>
> https://urldefense.com/v3/__https://github.com/apache/camel-karavan/discussions__;!!CiXD_PY!SbGh6yRHOwIAwegnsKdUtykGDSvbQ3iIVeToixq6eRplyr3cVpuz5U2aHqxJ5b0kzGQTcEdh0dfAcMSivvYBs5X8Cmo$
>
>
>
>
> On Thu, Jul 20, 2023 at 7:24 AM Claus Ibsen  wrote:
>
> > Hi
> >
> > I noticed that we are migrating some components to use camel-test-infra
> > for unit testing.
> > And I think it makes sense when you have
> >
> > - need to use docker / test-containers
> > - or to setup some internal embedded system that usually would require a
> > base class with some code to do that.
> >
> > However for basic components that are not in need for that then we should
> > not use camel-test-infra but just regular camel-test, just as camel end
> > users will do that.
> >
> > For example this PR
> >
> https://urldefense.com/v3/__https://github.com/apache/camel/pull/10739__;!!CiXD_PY!SbGh6yRHOwIAwegnsKdUtykGDSvbQ3iIVeToixq6eRplyr3cVpuz5U2aHqxJ5b0kzGQTcEdh0dfAcMSivvYBs_qR8OQ$
> >
> > I fail to see the need for test-infra-core for camel-asn1. This is just a
> > message transformation (dataformat) library that works purely in-memory.
> >
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2:
> https://urldefense.com/v3/__https://www.manning.com/ibsen2__;!!CiXD_PY!SbGh6yRHOwIAwegnsKdUtykGDSvbQ3iIVeToixq6eRplyr3cVpuz5U2aHqxJ5b0kzGQTcEdh0dfAcMSivvYBwcuHNv8$
>
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2:
> https://urldefense.com/v3/__https://www.manning.com/ibsen2__;!!CiXD_PY!SbGh6yRHOwIAwegnsKdUtykGDSvbQ3iIVeToixq6eRplyr3cVpuz5U2aHqxJ5b0kzGQTcEdh0dfAcMSivvYBwcuHNv8$
>
> As a recipient of an email from the Talend Group, your personal data will
> be processed by our systems. Please see our Privacy Notice <
> https://www.talend.com/privacy-policy/> for more information about our
> collection and use of your personal information, our security practices,
> and your data protection rights, including any rights you may have to
> object to automated-decision making or profiling we use to analyze support
> or marketing related communications. To manage or discontinue promotional
> communications, use the communication preferences portal<
> https://info.talend.com/emailpreferencesen.html>. To exercise your data
> protection rights, use the privacy request form<
> https://talend.my.onetrust.com/webform/ef906c5a-de41-4ea0-ba73-96c079cdd15a/b191c71d-f3cb-4a42-9815-0c3ca021704cl>.
> Contact us here  or by mail to either of
> our co-headquarters: Talend, Inc.: 400 South El Camino Real, Ste 1400, San
> Mateo, CA 94402; Talend SAS: 5/7 rue Salomon De Rothschild, 92150 Suresnes,
> France
>


-- 
Otavio R. Piske
http://orpiske.net

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

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Andrea!

On Thu, Jul 27, 2023 at 8:02 AM Andrea Cosentino  wrote:

> +1 (binding)
>
> Thanks Andrea
>
> Il giorno mer 26 lug 2023 alle ore 21:00 Andrea  ha
> scritto:
>
> > Hello all,
> >
> > This is a vote to release Apache Camel-kafka-connector 3.20.6
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1596
> >
> > Tag:
> >
> >
> https://gitbox.apache.org/repos/asf?p=camel-kafka-connector.git;a=tag;h=refs/tags/camel-kafka-connector-3.20.6
> >
> > 
> >
> > Please test this release candidate and cast your vote.
> > [ ] +1 Release the binary as  Apache Camel-kafka-connector 3.20.6
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Andrea.
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel 4.0.0-RC2

[Otavio Rodolfo Piske]

+1 (binding)

Tested on my own CI.

Thanks Gregor!

On Wed, Jul 26, 2023 at 9:37 AM Claus Ibsen  wrote:

> +1 (binding)
>
> Tested a little bit with jbang
>
> On Tue, Jul 25, 2023 at 2:21 PM Gregor Zurowski 
> wrote:
>
> > Hi Everyone:
> >
> > This is a vote to release the second release candidate for Apache
> > Camel 4.0.0 with 65 new features and improvements.
> >
> > Please note that Apache Camel Karaf is not part of this release cycle.
> >
> > Release notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353367=12311211
> >
> > == Apache Camel 4.0.0-RC2 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1594/
> >
> > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1594/org/apache/camel/camel/4.0.0-RC2/
> >
> > Tag: https://github.com/apache/camel/releases/tag/camel-4.0.0-RC2
> >
> > == Apache Camel Spring Boot 4.0.0-RC2 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1595/
> >
> > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1595/org/apache/camel/springboot/spring-boot/4.0.0-RC2/
> >
> > Tag:
> >
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.0.0-RC2
> >
> > Please test this release candidate and cast your vote:
> > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.0.0-RC2
> > [ ] -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
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [HEADS UP] - Removing camel-corda

[Otavio Rodolfo Piske]

+1

Thanks!

On Wed, Jul 26, 2023 at 2:32 PM Zineb Bendhiba 
wrote:

> +1
>
> Le mer. 26 juil. 2023 à 14:03, Claus Ibsen  a
> écrit :
>
> > Hi
> >
> > There is a blockchain component camel-corda that was added in late 2018,
> > that nobody really is using.
> >
> > It has a lot of old dependencies that are CVE affected and this becomes a
> > problem to maintain.
> >
> > The company behind the tech d3 don't really care and are working on a
> > next-gen v5 of their blockchain platform.
> >
> > So before we do GA of Camel v4 then I would like to remove it from v4 and
> > deprecate it in 3.22
> > https://issues.apache.org/jira/browse/CAMEL-19654
> >
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
>
> --
> Zineb
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Using camel-test-infra-core vs regular testing

[Otavio Rodolfo Piske]

On Mon, Jul 24, 2023 at 3:45 PM Nicolas Filotto  wrote:

> > One problem, IMHO, camel-test-junit5 already has a dependency chain that
> is
> > pretty complex, which is one of the things I wanted to solve ... But,
> more
>
> Sorry if it is a naive question but can't it be solved or at least
> improved directly at camel-test-junit5 level? But please note this artifact
> is relatively old (4 years) and the community doesn't seem to complain
> about it so much so I guess it is not really seen as a big issue.
>

I am not sure if we can fix it easily. Right now we have something like
this:

camel-test-junit5 -> depends on core components  -> depend on (some bits
of) core -> core components are depended by core

So, for any module that depends on camel-test-junit5, we have:

module -> camel-test-junit5 -> depends on core components  -> depend on
(some bits of) core -> core components are depended by core

I don't think it's the kind of problem our users would notice or complain
about. I do think, however, that it makes it much harder for us as
maintainers to understand the relationship between components and what each
one of them brings.


>
> > importantly, the problem is that I think it would be detrimental to Camel
> > and the community to have 2 test approaches (one based on the
> > CamelTestSupport and another based on the JUnit 5 extension), even if the
> > code is reorganized within camel-test-junit5.
>
> We already have 2 test approaches right now (even more if we count
> test-main and test-spring), the only difference is that there are in
> different artifacts. If your idea is to keep only one approach in the near
> future, in both cases, it means that we will need to deprecate some classes
> and then remove them. The only difference is that if we keep 2 artifacts,
> the old artifact will need to be deprecated too, and then removed entirely.
>

Yeah, my medium term plan was to, eventually, have the JUnit extension to
replace all of this. Of course, that would mean we could end up with some
specialized artifacts (each on their respective sub-project) for Spring
Boot and others (this is very speculative right now - just thinking freely
about the future state if we ever would do this).


>
> As you have mentioned before the CI is not stable enough, so it would be
> great if we could find a solution to make it more stable but I'm not really
> convinced that rewriting all the existing tests will help, IMHO, it is more
> a risk to add more flaky tests which would make the situation worse because
> it is a huge change so it is easy to make mistakes while migrating. I
> guess, I would be convinced if we could only migrate the unstable tests
> first to prove that it really helps, and if so I would be more than happy
> to give my +1 on it.
>

To be clear: the intention is not to rewrite "just to fix the CI". The
proposed feature offered a different way to manage the CamelContext (one
that would simplify and allow us to implement a range of new features).
Stability would eventually come as a constant effort to convert and
modernize the tests.

Testing is far harder than what we tend to give credit for and all I was
pointing out was that Camel - as great as it is - has a lot of technical
debt in terms of testing.

Also, some of the most stable tests we have are the ones that were
converted already: camel-amqp, camel-kafka, camel-mongodb, camel-cassandra,
camel-jms, camel-opensearch and camel-paho.

Naturally, from time to time some of them do fail - as for instance the
flakiness we are experiencing now with camel-jms - but given that it was
fairly stable on the CI up to a few days ago, it's probably because
something else disturbed them (I'm still investigating).



>
> As a recipient of an email from the Talend Group, your personal data will
> be processed by our systems. Please see our Privacy Notice <
> https://www.talend.com/privacy-policy/> for more information about our
> collection and use of your personal information, our security practices,
> and your data protection rights, including any rights you may have to
> object to automated-decision making or profiling we use to analyze support
> or marketing related communications. To manage or discontinue promotional
> communications, use the communication preferences portal<
> https://info.talend.com/emailpreferencesen.html>. To exercise your data
> protection rights, use the privacy request form<
> https://talend.my.onetrust.com/webform/ef906c5a-de41-4ea0-ba73-96c079cdd15a/b191c71d-f3cb-4a42-9815-0c3ca021704cl>.
> Contact us here  or by mail to either of
> our co-headquarters: Talend, Inc.: 400 South El Camino Real, Ste 1400, San
> Mateo, CA 94402; Talend SAS: 5/7 rue Salomon De Rothschild, 92150 Suresnes,
> France
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Camel 4.0-RC2 before GA

[Otavio Rodolfo Piske]

Maybe we can rename the profile from full to "release" and remove the
activation? So that, if we release the project using mvn -Prelease
release... it would be active?

On Mon, Jul 24, 2023 at 2:02 PM Claus Ibsen  wrote:

> Hi
>
> Okay so its very likely due to
> https://github.com/apache/camel/blame/main/apache-camel/pom.xml#L200
>
> This is now in a  that is skipped as part of the release build.
> Before it was not in a profile and included by default.
>
> How can we make the  trigger if either
>
> NOT -Dquickly
>
> or
>
> -Prelease
>
>
>
>
>
>
> On Mon, Jul 24, 2023 at 1:58 PM Claus Ibsen  wrote:
>
> >
> >
> > On Mon, Jul 24, 2023 at 1:41 PM Andrea Cosentino 
> > wrote:
> >
> >> Also without the tarball I guess also the website build would fail,
> >> because
> >> we won't have the source zip link to publish in the download table.
> >>
> >
> > Okay I created a ticket
> > https://issues.apache.org/jira/browse/CAMEL-19643
> >
> >
> >
> >>
> >> Il giorno lun 24 lug 2023 alle ore 13:35 Andrea Cosentino <
> >> anco...@gmail.com>
> >> ha scritto:
> >>
> >> > It's part of the release policy:
> >> >
> >> > https://www.apache.org/legal/release-policy.html#source-packages
> >> >
> >> > Il giorno lun 24 lug 2023 alle ore 13:26 Gregor Zurowski <
> >> > gre...@list.zurowski.org> ha scritto:
> >> >
> >> >> Is there anything by Apache that requires us to publish the source
> >> >> tarballs with the release?
> >> >>
> >> >> On Mon, Jul 24, 2023 at 1:19 PM Claus Ibsen 
> >> >> wrote:
> >> >> >
> >> >> > On Mon, Jul 24, 2023 at 1:12 PM Gregor Zurowski <
> >> >> gre...@list.zurowski.org>
> >> >> > wrote:
> >> >> >
> >> >> > > I have prepared the RC2 release, but I have noticed that the
> build
> >> is
> >> >> > > no longer creating "tarballs" of the main Camel distribution.
> >> >> > >
> >> >> > > This is the staging repository for 4.0.0-RC2:
> >> >> > >
> >> >>
> >> https://repository.apache.org/content/repositories/orgapachecamel-1592/
> >> >> > >
> >> >> > > Normally, the tarballs would be located here:
> >> >> > >
> >> >> > >
> >> >>
> >>
> https://repository.apache.org/content/repositories/orgapachecamel-1592/org/apache/camel/apache-camel/4.0.0-RC2/
> >> >> > >
> >> >> > > Is it possible that the revent Maven updates caused this?
> >> >> > >
> >> >> > >
> >> >> > Yes I would assume it's due to that. We can also argue what is the
> >> >> value of
> >> >> > such tarball, when everyone consumes Camel from maven central.
> >> >> > Lets create a JIRA and we can fix this for the GA release.
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > > Thanks in advance,
> >> >> > > Gregor
> >> >> > >
> >> >> > > On Sun, Jul 23, 2023 at 9:51 AM Claus Ibsen <
> claus.ib...@gmail.com
> >> >
> >> >> wrote:
> >> >> > > >
> >> >> > > > On Sun, Jul 23, 2023 at 9:47 AM Claus Ibsen <
> >> claus.ib...@gmail.com>
> >> >> > > wrote:
> >> >> > > >
> >> >> > > > >
> >> >> > > > >
> >> >> > > > > On Sun, Jul 23, 2023 at 9:44 AM Gregor Zurowski <
> >> >> > > gre...@list.zurowski.org>
> >> >> > > > > wrote:
> >> >> > > > >
> >> >> > > > >> Hi Claus,
> >> >> > > > >>
> >> >> > > > >> The branch is looking good, I am going to start with the
> >> release
> >> >> > > process
> >> >> > > > >> now.
> >> >> > > > >>
> >> >> > > > >>
> >> >> > > > > mvn release:prepare -Prelease -DdryRun
> >> >> > > > >
> >> >> > > > > [INFO] [ERROR] Failed to execute goal
> >> >> > > > > org.apache.maven.plugins:maven-gpg-plugin:3.1.0:sign
> (default)
> >> on
> >> >> > > project
> >> >> > > > > camel: Exit code: 2 -> [Help 1]
> >> >> > > > > I have this error locally, I have a fix .. but need 5 min to
> >> >> complete
> >> >> > > the
> >> >> > > > > build before pushing fix to main branch
> >> >> > > > >
> >> >> > > > >
> >> >> > > >
> >> >> > > >
> >> >> > > > ok just pushed
> >> >> > > >
> >> >> > >
> >> >>
> >>
> https://github.com/apache/camel/commit/2dc178385afe6163f4978113b63cd151e9b039a5
> >> >> > > >
> >> >> > > > Good luck with the release.
> >> >> > > >
> >> >> > > >
> >> >> > > >
> >> >> > > > >
> >> >> > > > >
> >> >> > > > >> Thanks,
> >> >> > > > >> Gregor
> >> >> > > > >>
> >> >> > > > >> On Fri, Jul 21, 2023 at 2:58 PM Claus Ibsen <
> >> >> claus.ib...@gmail.com>
> >> >> > > > >> wrote:
> >> >> > > > >> >
> >> >> > > > >> > Hi Gregor
> >> >> > > > >> >
> >> >> > > > >> > The main branch is ready for cutting 4.0.0-RC2.
> >> >> > > > >> >
> >> >> > > > >> >
> >> >> > > > >> > On Tue, Jul 11, 2023 at 8:37 PM Gregor Zurowski <
> >> >> > > > >> gre...@list.zurowski.org>
> >> >> > > > >> > wrote:
> >> >> > > > >> >
> >> >> > > > >> > > Sounds good to me. I will be available for cutting RC2
> by
> >> >> the end
> >> >> > > of
> >> >> > > > >> > > this month. I am also available for the GA release in
> the
> >> >> first
> >> >> > > three
> >> >> > > > >> > > weeks of August.
> >> >> > > > >> > >
> >> >> > > > >> > > Thanks,
> >> >> > > > >> > > Gregor
> >> >> > > > >> > >
> >> >> > > > >> > > On Tue, Jul 11, 2023 at 10:53 AM Claus Ibsen <
> >> >> > > 

Re: Using camel-test-infra-core vs regular testing

[Otavio Rodolfo Piske]

Hi,

On Mon, Jul 24, 2023 at 9:37 AM Nicolas Filotto  wrote:

> Hi,
>
> I tend to agree with Claus, camel-test-infra should be used only for
> integration tests for the reasons raised by Claus but also due to its name.
> It would be really misleading for the community to have to depend on an
> artifact called camel-test-infra for a unit test don't you agree?
>

Naming is hard ... So, yeah, maybe a better name could have prevented
confusion.



> In camel-test-junit5, Maybe we should do the same as what has been done in
> camel-test-main-junit5 where developers can decide to either extend
> CamelMainTestSupport or to use annotations like in SpringBoot and Quarkus
> or simply move the core logic of camel-test-infra into camel-test-junit5
> and make camel-test-infra depends on camel-test-junit5, WDYT?
>

One problem, IMHO, camel-test-junit5 already has a dependency chain that is
pretty complex, which is one of the things I wanted to solve ... But, more
importantly, the problem is that I think it would be detrimental to Camel
and the community to have 2 test approaches (one based on the
CamelTestSupport and another based on the JUnit 5 extension), even if the
code is reorganized within camel-test-junit5. I think it would also be
detrimental to the features I hoped we would develop in the future: they
would lack the maturity and stability from being extensively used to test
Camel itself. Ultimately, without community consensus on the suggested
approach, it would not attract contributions and would suffer too.

To be clear ... I am not trying to be an inflexible contributor or hard
headed person: I'd rather see my suggested feature (CAMEL-18957) go away
than leave the codebase in a worse state ... And I'd love to discuss
potential solutions that would allow us to develop those test features in
the future.

Kind regards


>
> Regards,
> Nicolas
>
>
> As a recipient of an email from the Talend Group, your personal data will
> be processed by our systems. Please see our Privacy Notice <
> https://www.talend.com/privacy-policy/> for more information about our
> collection and use of your personal information, our security practices,
> and your data protection rights, including any rights you may have to
> object to automated-decision making or profiling we use to analyze support
> or marketing related communications. To manage or discontinue promotional
> communications, use the communication preferences portal<
> https://info.talend.com/emailpreferencesen.html>. To exercise your data
> protection rights, use the privacy request form<
> https://talend.my.onetrust.com/webform/ef906c5a-de41-4ea0-ba73-96c079cdd15a/b191c71d-f3cb-4a42-9815-0c3ca021704cl>.
> Contact us here  or by mail to either of
> our co-headquarters: Talend, Inc.: 400 South El Camino Real, Ste 1400, San
> Mateo, CA 94402; Talend SAS: 5/7 rue Salomon De Rothschild, 92150 Suresnes,
> France
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Proposal for improving the way we collaborate on code improvements

[Otavio Rodolfo Piske]

Hi,

On Mon, Jul 24, 2023 at 9:47 AM Claus Ibsen  wrote:

> Hi
>
> Ad 1)
> For basic stuff like a polish or update in a readme / doc file then direct
> push can be okay.
>
> However the GA action has improved a lot in recent time, so the time it
> takes for it to complete and the feedback it gives now is more trustworthy.
>

Yeah. I think that with the GH actions we have now it is more feasible to
use a work strategy that favors PRs instead of direct push to main.

I wonder if it would be OK if we limit the direct pushes to docs and CI
code, while leaving the polishments and refactorings to go through the GH
workflow. There's always a risk with changing the code (even for small
changes) ...

What do you think?


>
> Ad 2)
> Yes this is good practice to squash - on GH I always click the "squash and
> merge" button.
>
> However locally I do individual commits while working on stuff, as
> sometimes I need to easier diff what I changed since something last was
> working etc.
>

Locally I apply a similar pattern as well.

Mostly I used rebase when merging, to simplify the bisect, But that
requires ensuring every single commit is compilable. It requires more
effort to do so (many times I had to squash, and run interactive rebases to
ensure the commits were perfectly clean and compilable).

I believe we have a consensus on this one (i.e.: that we should disable
rebase).


>
> On Wed, Jul 19, 2023 at 10:38 AM Otavio Rodolfo Piske <
> angusyo...@gmail.com>
> wrote:
>
> > Hi folks,
> >
> > I am writing this proposed changes based on the feedback received on the
> > previous email where I shared some thoughts/concerns about improving our
> > contribution practices (see the email entitled "Some thoughts on
> bisecting
> > Camel and our git commit practices" for details).
> >
> > This is mostly aimed at the Camel Core sub-project (potentially, we can
> use
> > it later for Camel Spring Boot, Camel Kafka Connector, and Camel Karaf).
> >
> > My understanding is that there are 2 practices we can start using that
> can
> > improve the quality of our commits and ensure our commits are compilable
> > and easy to bisect.
> >
> > 1. All code changes should done via Pull Requests:
> > The idea is to reduce the incidence of non-compilable commits by ensuring
> > that any code goes through Github compilation and testing.
> >
> > This helps both the contributors, by ensuring their contributions are
> > complete and testable as well as the rest of the community, by ensuring
> > that the code doesn't break the tree for others
> >
> > 2. Squashing as the default way of merging code
> > The idea is to make sure that the contribution is seen as a single unit
> of
> > change, including the build result of the contribution which reflects the
> > final state of the branch.
> >
> > There may be a few cases where going through this process might be a bit
> > too much. For instance: changing the code for CI automation, modifying
> code
> > that is clearly not compilable (i.e.: readme files or other text files
> that
> > are not documentation for the website, but provide support for
> developers,
> > etc).
> >
> > I suggest we use the same approach for these files, but don't necessarily
> > make ourselves bound to wait for the GH CI to run before merge.
> >
> > Please, what do you think about this? If there's agreement, how could we
> > possibly start using this process?
> >
> > Kind regards
> > --
> > Otavio R. Piske
> > http://orpiske.net
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Proposal for improving the way we collaborate on code improvements

[Otavio Rodolfo Piske]

Hi Andrea,

Thanks! After we get a consensus, I'll make sure we document that on the
contributor guidelines, so we have something to refer to and everyone knows
the expectations.

Kind regards

On Wed, Jul 19, 2023 at 10:47 AM Andrea Cosentino  wrote:

> Hello Otavio,
>
> I'm answering inline.
>
> Il giorno mer 19 lug 2023 alle ore 10:38 Otavio Rodolfo Piske <
> angusyo...@gmail.com> ha scritto:
>
> > Hi folks,
> >
> > I am writing this proposed changes based on the feedback received on the
> > previous email where I shared some thoughts/concerns about improving our
> > contribution practices (see the email entitled "Some thoughts on
> bisecting
> > Camel and our git commit practices" for details).
> >
> > This is mostly aimed at the Camel Core sub-project (potentially, we can
> use
> > it later for Camel Spring Boot, Camel Kafka Connector, and Camel Karaf).
> >
> > My understanding is that there are 2 practices we can start using that
> can
> > improve the quality of our commits and ensure our commits are compilable
> > and easy to bisect.
> >
> > 1. All code changes should done via Pull Requests:
> > The idea is to reduce the incidence of non-compilable commits by ensuring
> > that any code goes through Github compilation and testing.
> >
>
> I'm personally trying to open PR for any commit I want to push and the
> experience is good for the moment.
>
>
> >
> > This helps both the contributors, by ensuring their contributions are
> > complete and testable as well as the rest of the community, by ensuring
> > that the code doesn't break the tree for others
> >
> > 2. Squashing as the default way of merging code
> > The idea is to make sure that the contribution is seen as a single unit
> of
> > change, including the build result of the contribution which reflects the
> > final state of the branch.
> >
>
> We could disable the rebase and merge feature and only allow squash and
> merge. This is particularly important for verified commits, with rebase and
> merge the signature will be lost.
>
>
> >
> > There may be a few cases where going through this process might be a bit
> > too much. For instance: changing the code for CI automation, modifying
> code
> > that is clearly not compilable (i.e.: readme files or other text files
> that
> > are not documentation for the website, but provide support for
> developers,
> > etc).
> >
>
> I think we should write a paragraph in the contribution guide about this.
>
>
> >
> > I suggest we use the same approach for these files, but don't necessarily
> > make ourselves bound to wait for the GH CI to run before merge.
> >
>
> Yep.
>
> >
> > Please, what do you think about this? If there's agreement, how could we
> > possibly start using this process?
> >
>
> +1 for me.
>
>
> >
> > Kind regards
> > --
> > Otavio R. Piske
> > http://orpiske.net
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel K 2.0.0

[Otavio Rodolfo Piske]

+1 (binding)

Thanks!

On Thu, Jul 20, 2023 at 2:02 PM Andrea Cosentino  wrote:

> +1 (binding)
>
> Thanks Pasquale!
>
> Il giorno lun 17 lug 2023 alle ore 12:44 Pasquale Congiusti <
> pasquale.congiu...@gmail.com> ha scritto:
>
> > Hello,
> >
> > This is a vote to release Apache Camel K 2.0.0. The release also contains
> > the Camel K CRD 2.0.0, a Java client for Kubernetes Camel K CRDs. This
> > release is decoupled from the runtime, however it assumes as default (if
> > not specified by the user), Camel K Runtime version 2.16.0 (which is
> based
> > on Camel Quarkus 2.16.0 and Camel 3.20.1).
> >
> > This release contains several features and enhancements [1]. An upgrade
> > process from previous major version to this actual version is also
> > available in official documentation page [2]
> >
> > Camel K release files:
> > https://dist.apache.org/repos/dist/dev/camel/camel-k/2.0.0/
> >
> > Camel K Tag:
> > https://github.com/apache/camel-k/releases/tag/v2.0.0
> >
> > Camel K CRD Java dependency staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1591/
> >
> > Staging container image repository:
> > AMD64 architecture:
> >
> >
> https://hub.docker.com/layers/camelk/camel-k/2.0.0/images/sha256-caf48117e4384d90da1be8bf4d35243359d4e1fa3019f1322180b23c81ba9371?context=explore
> > ARM64
> > <
> https://hub.docker.com/layers/camelk/camel-k/2.0.0/images/sha256-caf48117e4384d90da1be8bf4d35243359d4e1fa3019f1322180b23c81ba9371?context=exploreARM64
> >
> > architecture (preview only):
> >
> >
> https://hub.docker.com/layers/camelk/camel-k/2.0.0-arm64/images/sha256-fbb5a0f630f7a67bfbb69465ab8e70948a3d44d4946f9ea8cb47869f36b00859?context=explore
> >
> > It's possible to install all staging artifacts with a single command
> > (preferably using the kamel CLI you find in Camel K release files):
> >
> > kamel install --operator-image=camelk/camel-k:2.0.0 --olm=false
> >
> > Please test this release candidate and cast your vote.
> >
> > [ ] +1 Release the binary as Apache Camel K 1.12.1 and Apache Camel K
> > Runtime 1.17.1
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > I start the vote with my +1.
> >
> > Thanks and regards,
> > Pasquale Congiusti
> >
> > [1] https://github.com/apache/camel-k/projects/22
> > [2] https://camel.apache.org/camel-k/next/contributing/upgrade.html
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Using camel-test-infra-core vs regular testing

[Otavio Rodolfo Piske]

st add a couple of annotations and JUnit handles the rest for
you (and you can focus on the routes and on the test). But, this does it
without requiring Spring (which, IMHO, is another benefit).

That said, although this is a topic I am intensely passionate about and I
truly believe this could open the room for a LOT more features for Camel,
our community and the vendors that build on top of Camel, I am not
interested in fractionating/disrupting the community over this. If the
consensus is that this is not the way to move forward, then I'll stop this
effort, revert the converted code and finish all work on this.

Kind regards


>
>
>
> On Thu, Jul 20, 2023 at 8:38 AM Otavio Rodolfo Piske  >
> wrote:
>
> > Hi Claus,
> >
> > test infra solves a few problems that we have in
> camel-test-support-junit5:
> > - it has a simpler dependency chain (it depends only on core)
> > - it allows managing the service ordering explicitly (i.e.: it's possible
> > to define in which order services can be initialized)
> > - it is much simpler and the JUnit 5 extension model gives us more
> > flexibility for additional features in the future (more on that later)
> > - it's not tightly coupled to one specific type of context or it's
> > lifecycle (i.e.: consider for instance how we have to set
> isUseRouteBuilder
> > to skip adding route builders on CamelTestSupport based tests)
> >
> > So, for instance, instead of tightly coupling a test to CamelTestSupport
> by
> > extending it ... we can just use JUnit's 5 extension model to add a
> context
> > to the test:
> >
> > @RegisterExtensionpublic static CamelContextExtension
> > camelContextExtension = new DefaultCamelContextExtension();
> >
> >
> > (+ the required setup of routes and context configuration - which is
> > required CamelTestSupport as well).
> >
> > Ultimately my hope is that we can harden this enough so that we can start
> > publicizing this to the end users and envolve it to support other
> features
> > (like Quarkus Continuous Testing - which, IMHO, would require a lot more
> > coordination with the service and context lifecycle than what we can do
> > with CamelTestSupport).
> >
> > What do you think?
> >
> > Kind regards
> >
> >
> > On Thu, Jul 20, 2023 at 7:24 AM Claus Ibsen 
> wrote:
> >
> > > Hi
> > >
> > > I noticed that we are migrating some components to use camel-test-infra
> > for
> > > unit testing.
> > > And I think it makes sense when you have
> > >
> > > - need to use docker / test-containers
> > > - or to setup some internal embedded system that usually would require
> a
> > > base class with some code to do that.
> > >
> > > However for basic components that are not in need for that then we
> should
> > > not use camel-test-infra but just regular camel-test, just as camel end
> > > users will do that.
> > >
> > > For example this PR
> > > https://github.com/apache/camel/pull/10739
> > >
> > > I fail to see the need for test-infra-core for camel-asn1. This is
> just a
> > > message transformation (dataformat) library that works purely
> in-memory.
> > >
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -
> > > @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >
> >
> >
> > --
> > Otavio R. Piske
> > http://orpiske.net
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Using camel-test-infra-core vs regular testing

[Otavio Rodolfo Piske]

Hi Claus,

test infra solves a few problems that we have in camel-test-support-junit5:
- it has a simpler dependency chain (it depends only on core)
- it allows managing the service ordering explicitly (i.e.: it's possible
to define in which order services can be initialized)
- it is much simpler and the JUnit 5 extension model gives us more
flexibility for additional features in the future (more on that later)
- it's not tightly coupled to one specific type of context or it's
lifecycle (i.e.: consider for instance how we have to set isUseRouteBuilder
to skip adding route builders on CamelTestSupport based tests)

So, for instance, instead of tightly coupling a test to CamelTestSupport by
extending it ... we can just use JUnit's 5 extension model to add a context
to the test:

@RegisterExtensionpublic static CamelContextExtension
camelContextExtension = new DefaultCamelContextExtension();


(+ the required setup of routes and context configuration - which is
required CamelTestSupport as well).

Ultimately my hope is that we can harden this enough so that we can start
publicizing this to the end users and envolve it to support other features
(like Quarkus Continuous Testing - which, IMHO, would require a lot more
coordination with the service and context lifecycle than what we can do
with CamelTestSupport).

What do you think?

Kind regards


On Thu, Jul 20, 2023 at 7:24 AM Claus Ibsen  wrote:

> Hi
>
> I noticed that we are migrating some components to use camel-test-infra for
> unit testing.
> And I think it makes sense when you have
>
> - need to use docker / test-containers
> - or to setup some internal embedded system that usually would require a
> base class with some code to do that.
>
> However for basic components that are not in need for that then we should
> not use camel-test-infra but just regular camel-test, just as camel end
> users will do that.
>
> For example this PR
> https://github.com/apache/camel/pull/10739
>
> I fail to see the need for test-infra-core for camel-asn1. This is just a
> message transformation (dataformat) library that works purely in-memory.
>
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Proposal for improving the way we collaborate on code improvements

[Otavio Rodolfo Piske]

Hi folks,

I am writing this proposed changes based on the feedback received on the
previous email where I shared some thoughts/concerns about improving our
contribution practices (see the email entitled "Some thoughts on bisecting
Camel and our git commit practices" for details).

This is mostly aimed at the Camel Core sub-project (potentially, we can use
it later for Camel Spring Boot, Camel Kafka Connector, and Camel Karaf).

My understanding is that there are 2 practices we can start using that can
improve the quality of our commits and ensure our commits are compilable
and easy to bisect.

1. All code changes should done via Pull Requests:
The idea is to reduce the incidence of non-compilable commits by ensuring
that any code goes through Github compilation and testing.

This helps both the contributors, by ensuring their contributions are
complete and testable as well as the rest of the community, by ensuring
that the code doesn't break the tree for others

2. Squashing as the default way of merging code
The idea is to make sure that the contribution is seen as a single unit of
change, including the build result of the contribution which reflects the
final state of the branch.

There may be a few cases where going through this process might be a bit
too much. For instance: changing the code for CI automation, modifying code
that is clearly not compilable (i.e.: readme files or other text files that
are not documentation for the website, but provide support for developers,
etc).

I suggest we use the same approach for these files, but don't necessarily
make ourselves bound to wait for the GH CI to run before merge.

Please, what do you think about this? If there's agreement, how could we
possibly start using this process?

Kind regards
-- 
Otavio R. Piske
http://orpiske.net

Camel Kafka Connector 4.x

[Otavio Rodolfo Piske]

Folks,

Some time ago I opened a PR aligning Camel Kafka Connector to Camel 4. I
haven't had much time yet to test it fully, investigate test logs/results,
etc. In case anyone wants to give it a try, review and comment, please take
a look at the following PR:
https://github.com/apache/camel-kafka-connector/pull/1538

Kind regards
-- 
Otavio R. Piske
http://orpiske.net

Re: Building quickly vs fastinstall (building test source???)

[Otavio Rodolfo Piske]

Hi Claus,

I haven't seen any replies to your comment so I am curious whether this is
still a problem? Apart from the occasional failures on the snapshot job
(which should be fixed now), I haven't noticed other problems ...

Kind regards

On Wed, Jul 5, 2023 at 9:32 AM Claus Ibsen  wrote:

> Hi
>
> On main its been optimized to build much faster now in quickly and
> fastinstall mode.
>
> However if I do a
>
> git clean -dXf
> git clean -df
>
> And then want to build everything (also unit test) then I suspect its no
> longer doing this
>
> mvn install -P fastinstall
>
> or with
>
> mvn install -D quickly
>
> It took 4 min to build on my computer (not using mvn demon or anything like
> that, just plain maven 3.9.2)
>
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Some thoughts on bisecting Camel and our git commit practices

[Otavio Rodolfo Piske]

Folks, thanks for the ideas here. Based on the suggestions provided, I'll
prepare a separate email with a list of ideas and propose some concrete
ideas for improving the way we collaborate on the project.

Kind regards

On Sat, Jun 24, 2023 at 7:06 AM Otavio Rodolfo Piske 
wrote:

> Andrea and Peter, I think you raised an important point about the CI:
> depending on what we decide, they are going to be even more critical to our
> workflow.
>
> I think the last few days have been outliers in terms of CI stability: the
> recent changes do touch on key parts of our build, so I think some level of
> instability it's OK until we sort out all the loose ends. We still have the
> eventual (OOM-related?) hang-up, but it seems to me that it's decreasing in
> frequency.
>
> In the end, I think if we adjust a bit the way we are working, it may even
> help with sorting out those instabilities: if we can bisect the code more
> easily, then it's going to be easier* to inspect those behaviors.
>
> *Obs. (OFF-TOPIC): In the future, we might even discuss with Infra about
> installing auto-bisect plugins on Jenkins or creating an auto-bisect job
> (I'll happily donate my scripts when we get to that point).
>
> Kind regards
>
> On Fri, Jun 23, 2023 at 5:19 PM Andrea Cosentino 
> wrote:
>
>> As of today, the CI build  (both Jenkins and Github action) is less
>> reliable than building locally.
>>
>> So, we could discuss if we could add some better rules in terms of
>> grouping
>> commits or use mandatory PRs, but I don't think we are at that level of
>> trust with CI.
>>
>> Il giorno ven 23 giu 2023 alle ore 17:13 Peter Palaga > >
>> ha scritto:
>>
>> > Thanks a lot Otavio, for bringing this up!
>> >
>> > I can only second Nicolas that CI should not be circumvented unless
>> > there is a serious reason.
>> > Second, PRs should ideally contain one compilable commit per logical
>> > change. As long as there is a just a single such commit in a PR, then
>> > the CI can work as a good barrier against broken commits.
>> >
>> > Otherwise it is up to the PR author to make sure that the individual
>> > commits are compilable too. I personally always try honor this rule. If
>> > my PR contains multiple commits, I often take care to re-order and/or
>> > fixup via git rebase --interactive. The readability of the history and
>> > the time of my co-workers matter to me.
>> >
>> > Thanks,
>> >
>> > -- Peter
>> >
>> > On 22/06/2023 10:12, Nicolas Filotto wrote:
>> > > Hi,
>> > >
>> > > For me, the best you can do to avoid this kind of problem is to avoid
>> > committing directly into the target branch by always submitting a PR for
>> > any change. And then, once the build is green, merge the PR with "Squash
>> > and merge" which is the default action on Camel. The action "Rebase and
>> > merge" should be avoided since the build result reflects the final
>> state of
>> > the branch, not the intermediate states. In case you need some changes
>> to
>> > fix the build, make sure to re-synchronize the source branch with the
>> > target branch, especially in case the changes are not done on the same
>> day
>> > because the Camel branches are modified very frequently and each change
>> can
>> > potentially be in conflicts with yours.
>> > >
>> > > it is a quite cumbersome approach but I don't see any safer way.
>> > >
>> > > Regards,
>> > > Nicolas
>> > > 
>> > > From: Otavio Rodolfo Piske 
>> > > Sent: Thursday, June 22, 2023 08:53
>> > > To: dev@camel.apache.org 
>> > > Subject: Re: Some thoughts on bisecting Camel and our git commit
>> > practices
>> > >
>> > > Hi,
>> > >
>> > > Release-tagged commits don't help here. The whole point of bisecting
>> is
>> > > finding out precisely which commit introduced a certain behavior or
>> bug,
>> > so
>> > > that I and other committers can diagnose, document and fix the
>> problem.
>> > > It's not possible to do that effectively with just release-tagged
>> > commits.
>> > >
>> > > Also, I don't think each commit needs to be "release quality": that
>> would
>> > > be too much right now. I do think, however, that each commit should be
>> > > compilable. Consider, for instance, the following commit patter

Re: Camel 4.0-RC2 before GA

[Otavio Rodolfo Piske]

Hi,

all in all +1 from me. It would be good to have a period to stabilize
things (build, tests, etc). IMHO, the idea of an RC2 fits well for this.

Kind regards

On Tue, Jul 11, 2023 at 10:53 AM Claus Ibsen  wrote:

> Hi
>
> I think it may be a good idea for us to do a RC2 before we do the 4.0 GA
> release.
>
> There has been some changes to the build system of the main branch, and
> many dependency upgrades (and some still to do) in both maven plugins and
> for components.
>
> All together I think it would be good to give time for doing a RC2 that
> allows us to catch and find issues ahead of time.
>
> So what if we aim for RC2 by the end of this month.
> And then cut 4.0 GA later in August.
>
> However it depends on the availability of Gregor. We can surely adjust the
> schedule.
> But I think the GA should be aimed to be GA in September; otherwise we
> postpone the release too long.
>
> Any thoughts?
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Integrating Apache Camel with OSSFuzz project

[Otavio Rodolfo Piske]

Hi Andrea,

+1 from me and I agree that it can help us uncover bugs and vulnerabilities.

Kind regards

On Wed, Jul 5, 2023 at 5:08 PM Andrea Cosentino  wrote:

> As far as I know, we need to provide a PR on their repository with some
> configuration (YAML) and a build file.
>
> They will build the project and attempt to fuzz in an automated way.
>
> So in our repositories nothing should be changed.
>
> Il giorno mer 5 lug 2023 alle ore 16:39 Pasquale Congiusti <
> pasquale.congiu...@gmail.com> ha scritto:
>
> > Hi Andrea,
> > any automation that helps us in having a better quality of software is
> > definitely good IMO. What it's not really clear to me is what kind of
> > additional development we should do and how much could be the cost of
> > maintenance if we include the project.
> >
> > Thanks,
> > Pasquale.
> >
> > On Tue, Jul 4, 2023 at 4:43 PM Andrea Cosentino 
> wrote:
> >
> > > Hello all,
> > >
> > > I was investigating Fuzzing and all the related tools today.
> > >
> > > I was already aware about OSSFuzz project and I verified some other
> > Apache
> > > Projects are already included [1]
> > >
> > > With this integration the project could be part of Fuzzing automation
> and
> > > get some report as Vulnerabilities or bugs.
> > >
> > > I think there is value in this kind of report, so I'd like to gather
> some
> > > more feedback and see if there is interest in the community.
> > >
> > > Thanks.
> > >
> > > [1] https://github.com/google/oss-fuzz/tree/master/projects
> > >
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: [VOTE] Release Apache Camel 4.0.0-RC1

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Gregor!

On Fri, Jun 30, 2023 at 9:31 AM Zheng Feng  wrote:

> +1 (non-binding)
>
> On Thu, Jun 29, 2023 at 7:17 PM Gregor Zurowski 
> wrote:
>
> > Hi Everyone:
> >
> > This is a vote to release the first release candidate for Apache Camel
> > 4.0.0 with 135 new features and improvements.
> >
> > Please note that Apache Camel Karaf is not part of this release cycle.
> >
> > Release notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353103=12311211
> >
> > == Apache Camel 4.0.0-RC1 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1583/
> >
> > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1583/org/apache/camel/apache-camel/4.0.0-RC1/
> >
> > Tag: https://github.com/apache/camel/releases/tag/camel-4.0.0-RC1
> >
> > == Apache Camel Spring Boot 4.0.0-RC1 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1584/
> >
> > Tag:
> >
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-4.0.0-RC1
> >
> > Please test this release candidate and cast your vote:
> > [ ] +1 Release the binary as Apache Camel and Camel Spring Boot 4.0.0-RC1
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
> >
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Release 4.0-RC1

[Otavio Rodolfo Piske]

There's a bunch of commits on main which fixed the same issue, so you can
try to cherry-pick those:

47c4a4e4502 (chores) build: fix CI build (camel-dsl)
7311a29f2bb  (chores) build: fix CI build (camel-olingo4-api)
3d167324d60  (chores) build: fix CI build (camel-olingo2-api)
76a5ee2188b  (chores) build: fix CI build (camel-dhis2-api)
88339326f47  (chores) build: fix CI build (camel-debezium-common)
93f454675ec  (chores) build: fix CI build (camel-box-api)
ab02143e7a8  (chores) build: fix CI build (camel-as2-api)
d6a1747b2d1  (chores) build: fix CI build (camel-fhir-api)
6f3083b5729  (chores) build: fix CI build (camel-spring-xml)

Kind regards

On Tue, Jun 27, 2023 at 1:41 PM Otavio Rodolfo Piske 
wrote:

> I think we can also try to remove the maven-source-plugin from those
> modules as it is already defined in the release profile.
>
>
> Kind regards
>
> On Tue, Jun 27, 2023 at 1:33 PM Claus Ibsen  wrote:
>
>> Hi
>>
>> I can get the build running with jar-no-fork but I get this a bit later
>>
>> [INFO] [INFO]
>> 
>> [INFO] [INFO] BUILD FAILURE
>> [INFO] [INFO]
>> 
>> [INFO] [INFO] Total time:  06:58 min
>> [INFO] [INFO] Finished at: 2023-06-27T13:29:03+02:00
>> [INFO] [INFO]
>> 
>> [INFO] [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-plugin-plugin:3.9.0:descriptor
>> (default-descriptor) on project camel-component-maven-plugin: Execution
>> default-descriptor of goal
>> org.apache.maven.plugins:maven-plugin-plugin:3.9.0:descriptor failed:
>> Negative time -> [Help 1]
>> [INFO] [ERROR]
>> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven
>> with
>> the -e switch.
>> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug
>> logging.
>> [INFO] [ERROR]
>> [INFO] [ERROR] For more information about the errors and possible
>> solutions, please read the following articles:
>> [INFO] [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
>> [INFO] [ERROR]
>> [INFO] [ERROR] After correcting the problems, you can resume the build
>> with
>> the command
>> [INFO] [ERROR]   mvn  -rf :camel-component-maven-plugin
>>
>>
>>
>> On Tue, Jun 27, 2023 at 1:19 PM Claus Ibsen 
>> wrote:
>>
>> > Hi
>> >
>> > Its like due to the maven source plugin is upgraded from 3.2.1 to 3.3.0
>> as
>> > part of apache 29 -> 30
>> > https://repo.maven.apache.org/maven2/org/apache/apache/29/apache-29.pom
>> > https://repo.maven.apache.org/maven2/org/apache/apache/30/apache-30.pom
>> >
>> > The SO has some hints
>> >
>> >
>> https://stackoverflow.com/questions/76305897/maven-build-fails-after-upgrading-to-maven-source-plugin-from-3-2-1-to-3-3-0
>> >
>> > So we can either downgrade to 3.2.1 (need to explicit do this in camel
>> > pom.xml files).
>> > Or try that workaround (from the SO link) with the jar -> jar-no-fork
>> >
>> > On Tue, Jun 27, 2023 at 11:45 AM Gregor Zurowski <
>> gre...@list.zurowski.org>
>> > wrote:
>> >
>> >> Hi Nicolas,
>> >>
>> >> I am running into the following error when starting the release prepare
>> >> phase:
>> >>
>> >> ```
>> >> [INFO] --- maven-source-plugin:3.3.0:jar-no-fork (attach-sources) @
>> >> camel-buildtools ---
>> >> [ERROR] We have duplicated artifacts attached.
>> >> [...]
>> >>  [INFO] Camel :: Buildtools  FAILURE [
>> >> 6.667 s]
>> >> ```
>> >>
>> >> And some additional info is logged afterwards:
>> >> ```
>> >> [ERROR] Failed to execute goal
>> >> org.apache.maven.plugins:maven-source-plugin:3.3.0:jar-no-fork
>> >> (attach-sources) on project camel-buildtools: Presumably you have
>> >> configured maven-source-plugn to execute twice times in your build.
>> >> You have to configure a classifier for at least on of them. -> [Help
>> >> 1]
>> >> ```
>> >>
>> >> This can be reproduced by running `./mvnw release:prepare -Prelease
>> >> -DdryRun` on the `release/4.0.0-RC1` branch.
>> >>
>> >> Any ideas on how to resolve this?
>> >>
>> >> Thanks

Re: Release 4.0-RC1

[Otavio Rodolfo Piske]

;
> >> > > nfilo...@talend.com> ha scritto:
> >> > >
> >> > >> It can be fixed for CR2 as it is a bug
> >> > >> 
> >> > >> From: Andrea Cosentino 
> >> > >> Sent: Friday, June 23, 2023 12:52
> >> > >> To: dev@camel.apache.org 
> >> > >> Subject: Re: Release 4.0-RC1
> >> > >>
> >> > >> Only DynamoDB is pending.
> >> > >>
> >> > >> We should also look at
> >> > >>
> >>
> https://urldefense.com/v3/__https://issues.apache.org/jira/browse/CAMEL-19491__;!!CiXD_PY!R1tHEs_usPa7jpnO3gRdctjxFY9JagIYl5-H2NjHlMNuhIsa8ZOAXOmwY_ww8vPqHGtlza6CR0rM8A8$
> >> > >> ,
> >> > >> because it seems we merged PRs based on wrong assumptions.
> >> > >>
> >> > >> Il giorno ven 23 giu 2023 alle ore 11:10 Nicolas Filotto <
> >> > >> nfilo...@talend.com> ha scritto:
> >> > >>
> >> > >> > Thanks Andrea, your ticket is the last one open for RC1 (
> >> > >> >
> >> > >>
> >>
> https://urldefense.com/v3/__https://issues.apache.org/jira/issues/?jql=project*20*3D*20CAMEL*20AND*20status*20in*20(Open*2C*20*22In*20Progress*22*2C*20Reopened)*20AND*20fixVersion*20*3D*204.0-RC1__;JSUlJSUlJSUlJSUlJSUlJSUlJQ!!CiXD_PY!R1tHEs_usPa7jpnO3gRdctjxFY9JagIYl5-H2NjHlMNuhIsa8ZOAXOmwY_ww8vPqHGtlza6CRoq6g1Q$
> >> > >> )
> >> > >> > so let us know when it is done.
> >> > >> >
> >> > >> > 
> >> > >> > From: Andrea Cosentino 
> >> > >> > Sent: Friday, June 23, 2023 11:04
> >> > >> > To: dev@camel.apache.org 
> >> > >> > Subject: Re: Release 4.0-RC1
> >> > >> >
> >> > >> >
> >> > >> >
> >> > >>
> >>
> https://urldefense.com/v3/__https://issues.apache.org/jira/browse/CAMEL-19159__;!!CiXD_PY!S96mm5MO4LYxsow3K5Vvmc0-hw8ms6GHGI0SDdMxf2aHbsD3V3IbVCUHE3eBfD2zfMDWT5k3VD3aHMA$
> >> > >> >
> >> > >> > Il giorno ven 23 giu 2023 alle ore 11:02 Nicolas Filotto <
> >> > >> > nfilo...@talend.com> ha scritto:
> >> > >> >
> >> > >> > > The 2 dependency upgrades left are fixed now.
> >> > >> > >
> >> > >> > > Andrea, what is the link to the issue you are fixing?
> >> > >> > > 
> >> > >> > > From: Andrea Cosentino 
> >> > >> > > Sent: Friday, June 23, 2023 10:16
> >> > >> > > To: dev@camel.apache.org 
> >> > >> > > Subject: Re: Release 4.0-RC1
> >> > >> > >
> >> > >> > > I would like to complete the AWS profile Credentials issues for
> >> all
> >> > >> the
> >> > >> > > components before RC1.
> >> > >> > >
> >> > >> > > I'll try to finish today.
> >> > >> > >
> >> > >> > > Il giorno ven 23 giu 2023 alle ore 09:55 Nicolas Filotto <
> >> > >> > > nfilo...@talend.com> ha scritto:
> >> > >> > >
> >> > >> > > > Hi,
> >> > >> > > >
> >> > >> > > > There are 2 dependency upgrades left before being ready for
> the
> >> > >> > release.
> >> > >> > > > Once merged, I will let you know.
> >> > >> > > >
> >> > >> > > > Regarding the release, Gregor, I don't know exactly what
> Claus
> >> does
> >> > >> to
> >> > >> > > > prepare it, but if I can help anyhow, please let me know.
> >> > >> > > >
> >> > >> > > > Regards,
> >> > >> > > > Nicolas
> >> > >> > > > 
> >> > >> > > > From: Otavio Rodolfo Piske 
> >> > >> > > > Sent: Friday, June 23, 2023 09:47
> >> > >> > > > To: dev@camel.apache.org 
> >> > >> > > > Subject: Re: Release 4.0-RC1
> >> > >>

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

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Gregor!

On Tue, Jun 27, 2023 at 10:21 AM Zheng Feng  wrote:

> +1 (non-binding)
>
> On Tue, Jun 27, 2023 at 12:06 AM Gregor Zurowski  >
> wrote:
>
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 3.21.0, a new LTS release with
> > 295 improvements and fixes.
> >
> > Release notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352568=12311211
> >
> > == Apache Camel 3.21.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1577/
> >
> > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1577/org/apache/camel/apache-camel/3.21.0/
> >
> > Tag: https://github.com/apache/camel/releases/tag/camel-3.21.0
> >
> > == Apache Camel Spring Boot 3.21.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1578/
> >
> > Tag:
> >
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.21.0
> >
> > == Apache Camel Karaf 3.21.0 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1579/
> >
> > Tag:
> https://github.com/apache/camel-karaf/releases/tag/camel-karaf-3.21.0
> >
> > Please test this release candidate and cast your vote:
> > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > Karaf 3.21.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

Re: Newcomer friendly default build, faster fast build and better reproducibility

[Otavio Rodolfo Piske]

Hi, yes we should.

Some days ago I created this task on the Camel Website, which is related to
reorganizing the contribution documentation:
https://github.com/apache/camel-website/issues/1017.

There should be some PRs this week reorganizing this.

Kind regards

On Tue, Jun 27, 2023 at 9:00 AM Claus Ibsen  wrote:

> Hi
>
> Thanks Peter for the quick build.
>
> I wonder if the building page should be updated (or have a section about
> quickly)
> https://camel.apache.org/manual/building.html
>
> Also if the auto formatting, source check etc are removed etc then this
> page may need to be updated
>
> On Fri, Jun 23, 2023 at 1:00 AM Peter Palaga  wrote:
>
> > Hi,
> >
> > In PR https://github.com/apache/camel/pull/10476 I tried to make some
> > changes to improve ergonomics and reproducibility.
> >
> > The first idea is to auto-fix formatting issues instead of outputting
> > error messages. I.e. rather than using Checkstyle plugin that is not
> > able to fix even basic violations of its policies, maven-license-plugin,
> > maven-formatter-plugin and maven-impsort-plugin are enabled by default
> > to format the sources in the desired way without contributors having to
> > configure their IDEs or anything else manually. There are some more
> > details in https://issues.apache.org/jira/browse/CAMEL-19461
> >
> > My second goal was to make the fast build (done from a state that passed
> > the CI) as fast as possible by removing the unessential Maven mojos from
> > the Maven execution plan altogether. We use this since longer in Camel
> > Quarkus and it is explained in detail in this blog:
> > https://peter.palaga.org/2020/10/29/skipping-maven-mojos-properly.html
> > The new mechanism is slightly different from how our original
> > `fastinstall` profile worked. `fastinstall` was disabling mojos by
> > defining their skip properties and it was activated simply by passing
> > `-Pfastinstall`. The new fast build does something different: it
> > disables the default `full` profile by passing a property. Because the
> > invocation had to change from -P to -D I dared to use the same property
> > name as we use in Camel Quarkus: `-Dquickly` I hope that's fine for
> > everybody. See also https://issues.apache.org/jira/browse/CAMEL-19466
> >
> > On my machine with 32 virtual threads, invoking `mvnd clean install
> > -Dquickly` takes
> >
> > * 1st build: 1m 21s
> > * 2nd build: 1m 10s
> >
> > The subsequent builds are slower. I have not investigated why, it is
> > perhaps because of garbage collection or some plugin might be leaking
> > memory.
> >
> > The third thing is not having the Apache Snapshots Maven repository
> > enabled by default for the sake of reproducibility locally and on CI.
> > It is still present in the `apache-snapshots` profile.
> > There are more details in
> > https://issues.apache.org/jira/browse/CAMEL-19465
> >
> > Any feedback is welcome.
> >
> > Thanks,
> >
> > -- Peter
> >
> >
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Newcomer friendly default build, faster fast build and better reproducibility

[Otavio Rodolfo Piske]

This patch provided a very nice improvement in terms of build speed for
Camel! I really like it.

That said, I believe we still have some areas where we could improve and
make our build even faster. I have just logged the issue CAMEL-19505 which
is related to a problem of our build compiling certain modules twice (due
to code generators the plugins being tied to a post-compilation phase).
This seems to be consuming precious seconds on the build.

https://issues.apache.org/jira/browse/CAMEL-19504

If anyone knowledgeable about Maven plugins wants to look at it, I think it
could provide another great productivity improvement for the whole
community.

Kind regards

On Fri, Jun 23, 2023 at 6:08 PM Babak Vahdat
 wrote:

> Thanks Peter!
>
> --
> Babak
>
> > Am 23.06.2023 um 16:55 schrieb Peter Palaga :
> >
> > Thanks for the feedback, Alex and Babak!
> >
> > I have found a way how -Pfastinstall could be handled as an alias of
> -Dquickly: https://github.com/apache/camel/pull/10483
> > Hope that solution is good enough to meet your needs?
> >
> > Thanks again,
> >
> > -- Peter
> >
> > On 23/06/2023 14:48, Babak Vahdat wrote:
> >>>> On 23 Jun 2023, at 14:27, Alexandre Gallice 
> wrote:
> >>>
> >>> Beyond bisect scripts, other developers could be impacted... it's a bit
> >>> like deprecating a profile.
> >>> For the sake of smooth transition, I wonder if it would be possible to
> have
> >>> something like the fastinstall profile setting -Dquickly and printing a
> >>> message that fastinstall might be possibly removed in the future.
> >>>
> >>> Alex
> >> Hi
> >> Yeah as that Maven profile has been exposed to the users as well since
> ages, so removing it (and asking them to adjust their settings.xml to
> achieve the same) doesn’t sound much “Newcomer friendly”:
> >>
> https://camel.apache.org/manual/building.html#_a_quick_build_without_running_tests
> <
> https://camel.apache.org/manual/building.html#_a_quick_build_without_running_tests
> >
> >> And thanks Peter a lot for his awesome work on his PR!
> >> --
> >> Babak
> >>>
> >>> On Fri, Jun 23, 2023 at 11:47 AM Otavio Rodolfo Piske <
> angusyo...@gmail.com>
> >>> wrote:
> >>>
> >>>> So, the primary reason I'd like to keep the fastinstall profile is
> because
> >>>> I bisect Camel often to find which commit introduced a certain bug,
> test
> >>>> failure or behavior. If we remove this profile, then I would have to
> adjust
> >>>> my bisect script so that in newer versions it uses "mvn -Dquickly"
> and in
> >>>> versions before this patch it would use "mvn -Pfastinstall" ... and I
> would
> >>>> have to, somehow, detect from when to start using one or the other (I
> think
> >>>> it would be difficult).
> >>>>
> >>>> I haven't thought about adding the profile to my user's settings.xml
> file,
> >>>> but maybe that would do the trick ... I'll give it a try.
> >>>>
> >>>> Regardless of that, the lack of fastinstall profile is not a blocker
> from
> >>>> my end. I think this is a good improvement.
> >>>>
> >>>> Kind regards
> >>>>
> >>>> On Fri, Jun 23, 2023 at 11:30 AM Peter Palaga 
> wrote:
> >>>>
> >>>>> On 23/06/2023 09:38, Otavio Rodolfo Piske wrote:
> >>>>>> +1 from me.
> >>>>>>
> >>>>>> All in all I think this is a good thing. Our build takes _way_ too
> >>>> long,
> >>>>> so
> >>>>>> any effort that can reduce this time is welcome. Also, I like that
> this
> >>>>>> would make the build similar to CEQ. Ideally, in the future, we
> could
> >>>>> also
> >>>>>> apply the same pattern to both CSB and CKC, so that we have an
> uniform
> >>>>>> build process across the board.
> >>>>>>
> >>>>>> That said, I have one (hopefully) simple request* in all of this:
> for
> >>>> us
> >>>>> to
> >>>>>> retain the fastinstall profile. The reason for me asking this is
> >>>> because
> >>>>> it
> >>>>>> makes my bisect scripts much easier.
> >>>>>>
> >>>>>> * Obs.: as far as I can tell, the PR does not remove the fastinst

Re: Some thoughts on bisecting Camel and our git commit practices

[Otavio Rodolfo Piske]

Andrea and Peter, I think you raised an important point about the CI:
depending on what we decide, they are going to be even more critical to our
workflow.

I think the last few days have been outliers in terms of CI stability: the
recent changes do touch on key parts of our build, so I think some level of
instability it's OK until we sort out all the loose ends. We still have the
eventual (OOM-related?) hang-up, but it seems to me that it's decreasing in
frequency.

In the end, I think if we adjust a bit the way we are working, it may even
help with sorting out those instabilities: if we can bisect the code more
easily, then it's going to be easier* to inspect those behaviors.

*Obs. (OFF-TOPIC): In the future, we might even discuss with Infra about
installing auto-bisect plugins on Jenkins or creating an auto-bisect job
(I'll happily donate my scripts when we get to that point).

Kind regards

On Fri, Jun 23, 2023 at 5:19 PM Andrea Cosentino  wrote:

> As of today, the CI build  (both Jenkins and Github action) is less
> reliable than building locally.
>
> So, we could discuss if we could add some better rules in terms of grouping
> commits or use mandatory PRs, but I don't think we are at that level of
> trust with CI.
>
> Il giorno ven 23 giu 2023 alle ore 17:13 Peter Palaga 
> ha scritto:
>
> > Thanks a lot Otavio, for bringing this up!
> >
> > I can only second Nicolas that CI should not be circumvented unless
> > there is a serious reason.
> > Second, PRs should ideally contain one compilable commit per logical
> > change. As long as there is a just a single such commit in a PR, then
> > the CI can work as a good barrier against broken commits.
> >
> > Otherwise it is up to the PR author to make sure that the individual
> > commits are compilable too. I personally always try honor this rule. If
> > my PR contains multiple commits, I often take care to re-order and/or
> > fixup via git rebase --interactive. The readability of the history and
> > the time of my co-workers matter to me.
> >
> > Thanks,
> >
> > -- Peter
> >
> > On 22/06/2023 10:12, Nicolas Filotto wrote:
> > > Hi,
> > >
> > > For me, the best you can do to avoid this kind of problem is to avoid
> > committing directly into the target branch by always submitting a PR for
> > any change. And then, once the build is green, merge the PR with "Squash
> > and merge" which is the default action on Camel. The action "Rebase and
> > merge" should be avoided since the build result reflects the final state
> of
> > the branch, not the intermediate states. In case you need some changes to
> > fix the build, make sure to re-synchronize the source branch with the
> > target branch, especially in case the changes are not done on the same
> day
> > because the Camel branches are modified very frequently and each change
> can
> > potentially be in conflicts with yours.
> > >
> > > it is a quite cumbersome approach but I don't see any safer way.
> > >
> > > Regards,
> > > Nicolas
> > > 
> > > From: Otavio Rodolfo Piske 
> > > Sent: Thursday, June 22, 2023 08:53
> > > To: dev@camel.apache.org 
> > > Subject: Re: Some thoughts on bisecting Camel and our git commit
> > practices
> > >
> > > Hi,
> > >
> > > Release-tagged commits don't help here. The whole point of bisecting is
> > > finding out precisely which commit introduced a certain behavior or
> bug,
> > so
> > > that I and other committers can diagnose, document and fix the problem.
> > > It's not possible to do that effectively with just release-tagged
> > commits.
> > >
> > > Also, I don't think each commit needs to be "release quality": that
> would
> > > be too much right now. I do think, however, that each commit should be
> > > compilable. Consider, for instance, the following commit pattern I
> notice
> > > when bisecting the code:
> > >
> > > commit1: TASK111: did some stuff  ---> not compilable
> > > commit2: TASK111: did some stuff  ---> compilable
> > > commit3: TASK111: did some stuff ---> not compilable
> > > commit4: TASK111: did some stuff ---> compilable
> > >
> > > Git bisect run is smart enough to skip commit2 and commit3 if given a
> > > proper exit code (that's what we do). However, the problem gets worse
> > once
> > > these compilable scripts start to pile up, such as:
> > >
> > > commit1: TASK111: did some stuff  ---> not compilable
> > &

Re: Newcomer friendly default build, faster fast build and better reproducibility

[Otavio Rodolfo Piske]

So, the primary reason I'd like to keep the fastinstall profile is because
I bisect Camel often to find which commit introduced a certain bug, test
failure or behavior. If we remove this profile, then I would have to adjust
my bisect script so that in newer versions it uses "mvn -Dquickly" and in
versions before this patch it would use "mvn -Pfastinstall" ... and I would
have to, somehow, detect from when to start using one or the other (I think
it would be difficult).

I haven't thought about adding the profile to my user's settings.xml file,
but maybe that would do the trick ... I'll give it a try.

Regardless of that, the lack of fastinstall profile is not a blocker from
my end. I think this is a good improvement.

Kind regards

On Fri, Jun 23, 2023 at 11:30 AM Peter Palaga  wrote:

> On 23/06/2023 09:38, Otavio Rodolfo Piske wrote:
> > +1 from me.
> >
> > All in all I think this is a good thing. Our build takes _way_ too long,
> so
> > any effort that can reduce this time is welcome. Also, I like that this
> > would make the build similar to CEQ. Ideally, in the future, we could
> also
> > apply the same pattern to both CSB and CKC, so that we have an uniform
> > build process across the board.
> >
> > That said, I have one (hopefully) simple request* in all of this: for us
> to
> > retain the fastinstall profile. The reason for me asking this is because
> it
> > makes my bisect scripts much easier.
> >
> > * Obs.: as far as I can tell, the PR does not remove the fastinstall
> > profile, so this is more like "just to be sure".
>
> Thanks for the feedback, Otavio! I actually wanted to remove the
> fastinstall profile altogether but now I see there are some leftovers.
> You mean you want to keep the fastinstall profile as it was with all
> those skip properties? I am open to that, but still, I wonder whether
> defining fastinstall in your settings.xml would not be a good enough
> solution too?
>
> -- P
>
> > Great work, Peter ... I'm hoping to see these changes merged.
> >
> > Kind regards
> >
> > On Fri, Jun 23, 2023 at 1:00 AM Peter Palaga  wrote:
> >
> >> Hi,
> >>
> >> In PR https://github.com/apache/camel/pull/10476 I tried to make some
> >> changes to improve ergonomics and reproducibility.
> >>
> >> The first idea is to auto-fix formatting issues instead of outputting
> >> error messages. I.e. rather than using Checkstyle plugin that is not
> >> able to fix even basic violations of its policies, maven-license-plugin,
> >> maven-formatter-plugin and maven-impsort-plugin are enabled by default
> >> to format the sources in the desired way without contributors having to
> >> configure their IDEs or anything else manually. There are some more
> >> details in https://issues.apache.org/jira/browse/CAMEL-19461
> >>
> >> My second goal was to make the fast build (done from a state that passed
> >> the CI) as fast as possible by removing the unessential Maven mojos from
> >> the Maven execution plan altogether. We use this since longer in Camel
> >> Quarkus and it is explained in detail in this blog:
> >> https://peter.palaga.org/2020/10/29/skipping-maven-mojos-properly.html
> >> The new mechanism is slightly different from how our original
> >> `fastinstall` profile worked. `fastinstall` was disabling mojos by
> >> defining their skip properties and it was activated simply by passing
> >> `-Pfastinstall`. The new fast build does something different: it
> >> disables the default `full` profile by passing a property. Because the
> >> invocation had to change from -P to -D I dared to use the same property
> >> name as we use in Camel Quarkus: `-Dquickly` I hope that's fine for
> >> everybody. See also https://issues.apache.org/jira/browse/CAMEL-19466
> >>
> >> On my machine with 32 virtual threads, invoking `mvnd clean install
> >> -Dquickly` takes
> >>
> >> * 1st build: 1m 21s
> >> * 2nd build: 1m 10s
> >>
> >> The subsequent builds are slower. I have not investigated why, it is
> >> perhaps because of garbage collection or some plugin might be leaking
> >> memory.
> >>
> >> The third thing is not having the Apache Snapshots Maven repository
> >> enabled by default for the sake of reproducibility locally and on CI.
> >> It is still present in the `apache-snapshots` profile.
> >> There are more details in
> >> https://issues.apache.org/jira/browse/CAMEL-19465
> >>
> >> Any feedback is welcome.
> >>
> >> Thanks,
> >>
> >> -- Peter
> >>
> >>
> >
>
>

-- 
Otavio R. Piske
http://orpiske.net

Re: Release 4.0-RC1

[Otavio Rodolfo Piske]

Hey Claus,

Absolutely. I don't have any big change on my end. My pre-release items
are:

- Fix the flaky tests on core and components
- Minor/safe cleanups here and there
- Multi-architecture build and test fixes

One note from my end: I'll also be on PTO from July 1st to July 9th. I can
come online for any emergency if necessary.

Now, asking both you and Gregor:

Is there something I can do to help make this release happen flawlessly? If
there's any, it will go to the top of my priority list. Just let me know.

Kind regards

On Thu, Jun 22, 2023 at 7:44 PM Claus Ibsen  wrote:

> Hi
>
> I think we are close to be good for RC1 as well.
> We can decide to move Kafka 3.5 upgrade for later.
> And Nicolas has some test / alignment on SB but that can be done later as
> well.
>
> I will be on PTO for 2 weeks, but it would be good to get RC1 released
> while I am away.
> Then I dont make trouble and commit a lot of stuff that breaks and whatnot
> ;)
>
> Otavio and Nicolas can you guys work on finializing and getting RC1 ready
> for Gregor to cut and release, thanks.
>
>
>
>
> On Wed, May 24, 2023 at 2:38 PM Claus Ibsen  wrote:
>
> > Hi
> >
> > I think within a few weeks we should close down and get the code base
> > ready for cutting RC1.
> > After the RC1 release we should then focus on stability and avoid doing
> > majar big changes.
> >
> > Then we could look at a 4.0 GA in July.
> >
> > Any thoughts?
> >
> >
> > --
> > Claus Ibsen
> > -
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
>
> --
> Claus Ibsen
> -
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Newcomer friendly default build, faster fast build and better reproducibility

[Otavio Rodolfo Piske]

+1 from me.

All in all I think this is a good thing. Our build takes _way_ too long, so
any effort that can reduce this time is welcome. Also, I like that this
would make the build similar to CEQ. Ideally, in the future, we could also
apply the same pattern to both CSB and CKC, so that we have an uniform
build process across the board.

That said, I have one (hopefully) simple request* in all of this: for us to
retain the fastinstall profile. The reason for me asking this is because it
makes my bisect scripts much easier.

* Obs.: as far as I can tell, the PR does not remove the fastinstall
profile, so this is more like "just to be sure".

Great work, Peter ... I'm hoping to see these changes merged.

Kind regards

On Fri, Jun 23, 2023 at 1:00 AM Peter Palaga  wrote:

> Hi,
>
> In PR https://github.com/apache/camel/pull/10476 I tried to make some
> changes to improve ergonomics and reproducibility.
>
> The first idea is to auto-fix formatting issues instead of outputting
> error messages. I.e. rather than using Checkstyle plugin that is not
> able to fix even basic violations of its policies, maven-license-plugin,
> maven-formatter-plugin and maven-impsort-plugin are enabled by default
> to format the sources in the desired way without contributors having to
> configure their IDEs or anything else manually. There are some more
> details in https://issues.apache.org/jira/browse/CAMEL-19461
>
> My second goal was to make the fast build (done from a state that passed
> the CI) as fast as possible by removing the unessential Maven mojos from
> the Maven execution plan altogether. We use this since longer in Camel
> Quarkus and it is explained in detail in this blog:
> https://peter.palaga.org/2020/10/29/skipping-maven-mojos-properly.html
> The new mechanism is slightly different from how our original
> `fastinstall` profile worked. `fastinstall` was disabling mojos by
> defining their skip properties and it was activated simply by passing
> `-Pfastinstall`. The new fast build does something different: it
> disables the default `full` profile by passing a property. Because the
> invocation had to change from -P to -D I dared to use the same property
> name as we use in Camel Quarkus: `-Dquickly` I hope that's fine for
> everybody. See also https://issues.apache.org/jira/browse/CAMEL-19466
>
> On my machine with 32 virtual threads, invoking `mvnd clean install
> -Dquickly` takes
>
> * 1st build: 1m 21s
> * 2nd build: 1m 10s
>
> The subsequent builds are slower. I have not investigated why, it is
> perhaps because of garbage collection or some plugin might be leaking
> memory.
>
> The third thing is not having the Apache Snapshots Maven repository
> enabled by default for the sake of reproducibility locally and on CI.
> It is still present in the `apache-snapshots` profile.
> There are more details in
> https://issues.apache.org/jira/browse/CAMEL-19465
>
> Any feedback is welcome.
>
> Thanks,
>
> -- Peter
>
>

-- 
Otavio R. Piske
http://orpiske.net

Re: Some thoughts on bisecting Camel and our git commit practices

[Otavio Rodolfo Piske]

Hi,

Release-tagged commits don't help here. The whole point of bisecting is
finding out precisely which commit introduced a certain behavior or bug, so
that I and other committers can diagnose, document and fix the problem.
It's not possible to do that effectively with just release-tagged commits.

Also, I don't think each commit needs to be "release quality": that would
be too much right now. I do think, however, that each commit should be
compilable. Consider, for instance, the following commit pattern I notice
when bisecting the code:

commit1: TASK111: did some stuff  ---> not compilable
commit2: TASK111: did some stuff  ---> compilable
commit3: TASK111: did some stuff ---> not compilable
commit4: TASK111: did some stuff ---> compilable

Git bisect run is smart enough to skip commit2 and commit3 if given a
proper exit code (that's what we do). However, the problem gets worse once
these compilable scripts start to pile up, such as:

commit1: TASK111: did some stuff  ---> not compilable
commit2: TASK111: did some stuff  ---> compilable
commit3: TASK111: did some stuff ---> not compilable
commit4: TASK111: did some stuff ---> compilable
commit5: TASK222: did some stuff  ---> not compilable
commit6: TASK222: did some stuff  ---> compilable
commit7: TASK222: did some stuff ---> not compilable
commit8: TASK222: did some stuff ---> compilable

At some point, the bisect execution runs out of skippable commits and you
have to: a) test manually, b) restart the bisect operation with different
good/bad commits, or c) investigate the list of skipped commits one by one.

The same can happen when merging community contributions composed of
multiple commits.

So, I think we can improve here by doing 2 things:

1. When commiting the work on a task, making sure that every commit is
compilable. For instance, in the pattern above, by squashing
commit1+commit2, commit3+4, etc.
2. When merging community contributions with multiple PRs, squashing the
contribution before merging - if suspicious that one or more of the commits
introduce uncompilable changes.

If we start doing this now, bisecting will be much easier in the future.

Kind regards

On Thu, Jun 22, 2023 at 8:08 AM Petr Kuzel 
wrote:

> Hi Otavio,
>
> the codebase does not have the release quality
> after each commit. Test-driven development could
> even invite devs to separately commit failing tests
> as a proof they are effective.
>
> On contrary the release-tagged commits should
> be safe. Would not help you to focus
> on the release-tagged commits only, pls?


>   Hope it helps
>   Cc.
>
> --
>   Mr. Petr Kužel, Software Engineer
>   Eurofins International Support Services s.à r.l.
>   Val Fleuri 23
>   L-1526 LUXEMBOURG
>
> -Original Message-
> From: Otavio Rodolfo Piske 
> Sent: Wednesday, June 21, 2023 11:17
> To: dev 
> Subject: Some thoughts on bisecting Camel and our git commit practices
>
>
> Folks,
>
> You may have seen that PRs constantly report failures when testing changes
> on core. This is almost always caused by flaky tests.
>
> I have been trying to find the root causes of those flaky tests. Quite
> often this involves going all the way to early versions of Camel 3 to find
> stable executions of those tests.
>
> The investigation itself is mostly automated by using git bisect run ...
> This significantly improves the developer ability to find the root causes
> of issues.
>
> Despite all this automation, however, the task has been ... quite difficult
> and lengthy. Even considering the extensive resources I have access to
> (thanks to my employer), bisecting a single test failure can take several
> *days*.
>
> In particular, this investigation has been difficult because we have a huge
> amount of dirty commits on the tree: partially modified work, uncompilable
> changes, broken tests and more.
>
> While it's NOT my intention to suggest introducing/discussing a full blown
> clean commit policy, I do wonder if we have some room to discuss how we can
> improve the way we work to ensure that the tree is compilable and somewhat
> testable (and, possibly, enforce that).
>
> We cannot fix the git history of the project, but we can ensure that future
> investigation can be made much easier in the future.
>
> So, folks, does anyone have any suggestions about how we could improve
> here?
>
> Kind regards
> --
> Otavio R. Piske
> http://orpiske.net/
>


-- 
Otavio R. Piske
http://orpiske.net

Some thoughts on bisecting Camel and our git commit practices

[Otavio Rodolfo Piske]

Folks,

You may have seen that PRs constantly report failures when testing changes
on core. This is almost always caused by flaky tests.

I have been trying to find the root causes of those flaky tests. Quite
often this involves going all the way to early versions of Camel 3 to find
stable executions of those tests.

The investigation itself is mostly automated by using git bisect run ...
This significantly improves the developer ability to find the root causes
of issues.

Despite all this automation, however, the task has been ... quite difficult
and lengthy. Even considering the extensive resources I have access to
(thanks to my employer), bisecting a single test failure can take several
*days*.

In particular, this investigation has been difficult because we have a huge
amount of dirty commits on the tree: partially modified work, uncompilable
changes, broken tests and more.

While it's NOT my intention to suggest introducing/discussing a full blown
clean commit policy, I do wonder if we have some room to discuss how we can
improve the way we work to ensure that the tree is compilable and somewhat
testable (and, possibly, enforce that).

We cannot fix the git history of the project, but we can ensure that future
investigation can be made much easier in the future.

So, folks, does anyone have any suggestions about how we could improve
here?

Kind regards
-- 
Otavio R. Piske
http://orpiske.net

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

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Gregor!

On Fri, Jun 16, 2023 at 6:59 PM Babak Vahdat
 wrote:

> +1 (binding)
>
> Thanks Gregor!
>
> --
> Babak
>
> > On 16 Jun 2023, at 07:47, Gregor Zurowski 
> wrote:
> >
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 3.20.6 (LTS), a patch release
> > with 20 fixes and improvements.
> >
> > Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353270=12311211
> >
> > == Apache Camel 3.20.6 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1574/
> >
> > Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1574/org/apache/camel/apache-camel/3.20.6/
> >
> > Tag: https://github.com/apache/camel/releases/tag/camel-3.20.6
> >
> > == Apache Camel Spring Boot 3.20.6 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1575/
> >
> > Tag:
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.20.6
> >
> > == Apache Camel Karaf 3.20.6 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1576/
> >
> > Tag:
> https://github.com/apache/camel-karaf/releases/tag/camel-karaf-3.20.6
> >
> > Please test this release candidate and cast your vote:
> > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > Karaf 3.20.6
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
>
>

-- 
Otavio R. Piske
http://orpiske.net

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

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Gregor!

Kind regards

On Thu, Jun 15, 2023 at 7:23 PM Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> Regards
> JB
>
> On Wed, Jun 14, 2023 at 7:47 AM Gregor Zurowski
>  wrote:
> >
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 3.14.9, a new patch release
> > with 2 improvements and fixes.
> >
> > Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353269=12311211
> >
> > == Apache Camel 3.14.9 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1571/
> >
> > Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1571/org/apache/camel/apache-camel/3.14.9/
> >
> > Tag: https://github.com/apache/camel/releases/tag/camel-3.14.9
> >
> > == Apache Camel Spring Boot 3.14.9 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1572/
> >
> > Tag:
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.14.9
> >
> > == Apache Camel Karaf 3.14.9 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1573/
> >
> > Tag:
> https://github.com/apache/camel-karaf/releases/tag/camel-karaf-3.14.9
> >
> > Please test this release candidate and cast your vote:
> > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > Karaf 3.14.9
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
>


-- 
Otavio R. Piske
http://orpiske.net

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

[Otavio Rodolfo Piske]

+1 (binding)

Thanks Gregor!

On Mon, Jun 12, 2023 at 11:18 AM Andrea Cosentino  wrote:

> +1 (binding)
>
> Thanks Gregor!
>
> Il giorno lun 12 giu 2023 alle ore 10:21 Gregor Zurowski <
> gre...@list.zurowski.org> ha scritto:
>
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 3.18.8, a new patch release
> > with 8 improvements and fixes.
> >
> > Release notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353276=12311211
> >
> > == Apache Camel 3.18.8 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1568/
> >
> > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1568/org/apache/camel/apache-camel/3.18.8/
> >
> > Tag: https://github.com/apache/camel/releases/tag/camel-3.18.8
> >
> > == Apache Camel Spring Boot 3.18.8 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1569/
> >
> > Tag:
> >
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.18.8
> >
> > == Apache Camel Karaf 3.18.8 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1570/
> >
> > Tag:
> https://github.com/apache/camel-karaf/releases/tag/camel-karaf-3.18.8
> >
> > Please test this release candidate and cast your vote:
> > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > Karaf 3.18.8
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Re: Draft Camel Board Report for June 2023

[Otavio Rodolfo Piske]

Hi Andrea, it looks good to me.

Thanks!

On Mon, Jun 12, 2023 at 9:55 AM Andrea Cosentino  wrote:

> Thanks Pasquale, reposting here:
>
> ## Description:
> The mission of Apache Camel is the creation and maintenance of an
> open-source
> integration framework based on known Enterprise Integration Patterns.
>
> ## Project Status:
> Project status: Ongoing with high activity
> Issues: There are no issues requiring board attention at this time.
>
> ## Membership Data:
> Apache Camel was founded 2008-12-17 (14 years ago)
> There are currently 87 committers and 44 PMC members in this project.
> The Committer-to-PMC ratio is roughly 2:1.
>
> Community changes, past quarter:
> - Nicolas Filotto was added to the PMC on 2023-04-05
> - Christoph Deppisch was added as committer on 2023-05-25
> - Marcin Grzejszczak was added as committer on 2023-04-20
>
> ## Project Activity:
> - We released Camel 3.14.8
> - We released Camel 3.18.6
> - We released Camel 3.18.7
> - We released Camel 3.20.3
> - We released Camel 3.20.4
> - We released Camel 3.20.5
> - We released Camel 4.0.0-M2
> - We released Camel 4.0.0-M3
> - Note: Camel releases have synchronized releases of Camel-Karaf and
>   Camel-Spring-Boot too for 3.x, while for 4.x only Camel-Spring-Boot is
>   synchronized.
> - We are near releasing the first release candidate for Camel 4.0.0, it
> will
>   be done in this month and we plan to complete 4.0.0 release in September.
> - We are continuing release 3.18.x LTS release train and we are in the
> process
>   of releasing the next patch release.
> - We started the release train for 3.20.x LTS, and we are already at the
> fifth
>   patch release.
> - We are still supporting Camel 3.14.x, an LTS train, but it's going EOL,
> so
>   there will be one last release.
> - For Camel K we are working on releasing the first patch release for
> 1.12.x,
>   but the focus is on the 2.x work. We are focusing on giving to the
> community
>   a new experience.
> - For Camel-Kamelets releases
> - We released Camel Kameletes 0.9.4
> - We released Camel Kameletes 3.20.3
> - We released Camel Kameletes 3.20.4
> - We released Camel Kameletes 3.20.5
> - We released Camel Kamelets 4.0.0-M2
> - We released Camel Kamelets 4.0.0-M3
> - We are improving the Camel-K experience and Camel Kamelets is already
>   looking at Camel 4
> - Camel-Kamelets is not only related to camel k anymore so it could be used
>   with all the Camel's flavours
> - The Camel-Quarkus work is going ahead following the main camel releases
> with
>   multiple releases
> - We released Camel-quarkus 2.13.3
> - We released Camel-quarkus 3.0.0-M1
> - We released Camel-quarkus 3.0.0-M2
> - Camel-Kameleon and Camel-Karavan are improving and more and more
>   contributors are starting to help. We are improving the projects by
>   supporting new features and aligning with LTS releases 3.20.x as in the
> last
>   report
> - Camel Kafka Connector release based on Camel 3.20.1 has been released.
> - We are supporting Camel Kafka Connector aligning it to the Camel Core LTS
>   Releases 3.20.x and we released camel-kafka-connector 3.20.3
> - Generally speaking we are working on supporting Camel 4 in all the
> runtimes
>   provided and this is taking a lot of effort.
>
> ## Community Health:
> - 265 issues opened in JIRA, past quarter (25% decrease) and 284 issues
> closed
>   in JIRA, past quarter (3% decrease): We are in a stabilization phase for
>   Camel 3.x and the LTS are more or less stable. Mostly new issues are
> about
>   Camel 4.x, but since we are closing down the work for releasing Camel
> 4.0.0
>   there is less new issues opened.
> - 211 issues opened on GitHub, past quarter (13% decrease) and 203 issues
>   closed on GitHub, past quarter (4% decrease): Since we are working on
>   releasing Camel 4.0.0 some of the subprojects using gh issues are seeing
>   less focused work, Camel is using JIRA for tracking the work
> - 4648 commits in the past quarter (3% increase) and 120 code contributors
> in
>   the past quarter (no change): More or less we are stable. The camel core
>   team is focusing on Camel 4.x. We saw sporadic contributions from new
>   contributors.
> - 1362 PRs opened on GitHub, past quarter (7% increase) and 1366 PRs closed
> on
>   GitHub, past quarter (7% increase): on some of the subprojects the
> activity
>   is slowing down for stabilization reasons, we also cleaned up some of the
>   subprojects gh PR and there was a lot of work on Camel-Kamelets from this
>   pov
> - dev@camel.apache.org had a 32% decrease in traffic in the past quarter
> (304
>   emails compared to 441): This is mostly because the work done on Camel 4
>   side is about moving to support Jakarta, there was some discussions but
>   mostly about releasing.
> - iss...@camel.apache.org had a 0% increase in traffic in the past quarter
>   (1901 emails compared to 1891): We are more or less stable here. There
> was
>   activity in JIRA mostly for Camel 4 work and cleaning up.
> - 

[HEADS UP] Regen bot

[Otavio Rodolfo Piske]

Hi folks,

This is just a heads up that since a few days ago the regen bot started to
provide some bogus commits - even suggesting broken code.

Andrea C. and I are keeping an eye on it and we have already applied a fix.
In the meantime, I'd kindly advise you to beware with merging those pull
requests.

Kind regards
-- 
Otavio R. Piske
http://orpiske.net

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

[Otavio Rodolfo Piske]

+1 (binding)

Tested on my own CI

Thanks!!!

Kind regards

On Wed, May 24, 2023 at 12:05 PM Gaëlle Fournier <
gaelle.fournier.w...@gmail.com> wrote:

> +1 (non-binding)
>
> Thanks Gregor,
>
> Le mer. 24 mai 2023 à 07:51, Gregor Zurowski  a
> écrit :
>
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 3.14.8, a new patch release
> > with 14 improvements and fixes.
> >
> > Release notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352676=12311211
> >
> > == Apache Camel 3.14.8 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1561/
> >
> > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1561/org/apache/camel/apache-camel/3.14.8/
> >
> > Tag: https://github.com/apache/camel/releases/tag/camel-3.14.8
> >
> > == Apache Camel Spring Boot 3.14.8 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1562/
> >
> > Tag:
> >
> https://github.com/apache/camel-spring-boot/releases/tag/camel-spring-boot-3.14.8
> >
> > == Apache Camel Karaf 3.14.8 ==
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1563/
> >
> > Tag:
> https://github.com/apache/camel-karaf/releases/tag/camel-karaf-3.14.8
> >
> > Please test this release candidate and cast your vote:
> > [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> > Karaf 3.14.8
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
> >
>


-- 
Otavio R. Piske
http://orpiske.net