+1 (binding)
Thanks Andrea!
--
Babak
> Am 19.02.2024 um 15:15 schrieb Andrea Cosentino :
>
> Hello all,
>
> This is a vote for releasing camel-kamelets 4.4.0
>
> This is the first release of camel-kamelets supporting LTS Camel 4.4.0 and
> it contains many new Kamelets and a lot of fixes.
>
+1 (non binding)
--
Claudio Miranda
clau...@claudius.com.br
http://www.claudius.com.br
+1 (binding)
De : Claus Ibsen
Envoyé : lundi 19 février 2024 15:19
À : dev@camel.apache.org
Cc : us...@camel.apache.org
Objet : Re: [VOTE] Release Apache Camel Kamelets 4.4.0
CAUTION: This email originated from outside of the organization. Do not click
+1 (binding)
On Mon, Feb 19, 2024 at 3:14 PM Andrea Cosentino wrote:
> Hello all,
>
> This is a vote for releasing camel-kamelets 4.4.0
>
> This is the first release of camel-kamelets supporting LTS Camel 4.4.0 and
> it contains many new Kamelets and a lot of fixes.
>
> Kamelets release files:
Hello all,
This is a vote for releasing camel-kamelets 4.4.0
This is the first release of camel-kamelets supporting LTS Camel 4.4.0 and
it contains many new Kamelets and a lot of fixes.
Kamelets release files:
https://dist.apache.org/repos/dist/dev/camel/camel-kamelets/4.4.0
Kamelets staging
Hi
Yeah ideally those CVEs should be in 1 merge to main - so they were
released together.
And frankly the website is rebuild from scratch each time, instead of being
able to update only parts of it.
The CVEs only affect the security page + a new page per CVE.
I stopped one of the builds, as
I don't think it would work on our website, but Zoran could have more
information about this.
What we could do, it's maybe limit the number of builds on git-websites
nodes concurrently.
Il giorno lun 19 feb 2024 alle ore 13:30 Christofer Dutz <
christofer.d...@c-ware.de> ha scritto:
> Hi,
>
>
Hi,
as the PLC4X build also uses that, perhas what we did would be also an option
for you?
We build the website on our own VM, but stash the built website … then on the
git-websites agent, we simply unstash what was built on our VM and deploy that
… this reduces the lock we have on shared
I think Zoran Regvart is able to give more advice on this, but yes, the
build should be on git-websites labeled nodes.
But again, this is a really a particular case: there were 3 CVEs and two
blog posts all in once.
Also, when a PR is merged, the website build starts immediately and it
takes a
Usually there is not that much activities. There were 3 PRs related to cves
and some related to the last release done during the weekend. So this
should be just a temporary saturation. We don't have other way of
publishing the website except using that mechanism.
Il lun 19 feb 2024, 13:13
Hi all,
I’m currently trying to finish up some stuff for the upcoming PLC4X release.
However am having problems because every time I want to update our website, I
have to wait a long, long time, because all 3 runners in the “git-websites”
class (websites1, websites2 and websites3) are blocked
11 matches
Mail list logo