Dear Camel devs and users,
on behalf of Apache Camel PMC I'm happy to announce the general
availability of Camel K version 2.0 [1] [1a] [1b].
This major version release is an important milestone as it provides a
series of new exciting features that will simplify the management and
operations of yo
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
> improv
> 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
On Mon, Jul 24, 2023 at 2:20 PM Gregor Zurowski
wrote:
> I will restart the release then. Should I cherry-pick both commits
> (https://github.com/apache/camel/pull/10805/commits) or just 75b75809?
>
>
Yes ideally both of them.
> On Mon, Jul 24, 2023 at 2:16 PM Claus Ibsen wrote:
> >
> > On Mo
I will restart the release then. Should I cherry-pick both commits
(https://github.com/apache/camel/pull/10805/commits) or just 75b75809?
On Mon, Jul 24, 2023 at 2:16 PM Claus Ibsen wrote:
>
> On Mon, Jul 24, 2023 at 2:08 PM Otavio Rodolfo Piske
> wrote:
>
> > Maybe we can rename the profile fro
On Mon, Jul 24, 2023 at 2:08 PM Otavio Rodolfo Piske
wrote:
> 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?
>
>
Yeah that seems to work
https://github.com/apache/camel/pul
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/bla
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: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
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.
Il giorno lun 24 lug 2023 alle ore 13:35 Andrea Cosentino
ha scritto:
> It's part of the release policy:
>
> https://www.apache.org/legal/release-policy
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?
>
>
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
> wrote:
>
> > I have prepared the RC2 release, but I have noticed that the build is
> > no longer
On Mon, Jul 24, 2023 at 1:12 PM Gregor Zurowski
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/org
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:
h
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
> arti
Hello all,
The vote passed with the following result:
9 +1 binding votes: Andrea Cosentino, Claus Ibsen, Pasquale Congiusti,
Zineb Bendhiba, Claudio Miranda, Otavio R. Piske, Jon Anstey, Cristoph
Deppisch and Jean-Baptiste Onofrè
1 +1 non-binding votes: Gaelle Fournier
I'm finalizing the post
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
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.
>
>
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.
Ad 2)
Yes this is good practice to squash - on
Hi,
+1 with this proposal, thx Otavio
Regards,
Nicolas
From: Otavio Rodolfo Piske
Sent: Wednesday, July 19, 2023 10:38
To: dev
Subject: Proposal for improving the way we collaborate on code improvements
Hi folks,
I am writing this proposed changes based on the
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?
In came
21 matches
Mail list logo
