+1 (binding)
On Fri, Oct 1, 2021 at 9:55 PM Zineb Bendhiba wrote:
>
> Hello,
>
> This is a vote to release Apache Camel Quarkus 2.3.0.
>
> Highlights:
>
> * Quarkus 2.3.0.Final
> * Fixed issues:
> https://github.com/apache/camel-quarkus/milestone/19?closed=1
> * All commits:
>
I looked at camel-spring-boot a little bit and have several questions and
suggestions… if there’s agreement I’ll open some issues and work on them.
1. The AsciiDoc pages are only included in the main component/dataformat/…
pages, and not accessible through navigation standalone. I think they
+1 (non-binding)
Thanks Zineb!
Freeman
On Fri, Oct 1, 2021 at 3:55 PM Zineb Bendhiba
wrote:
> Hello,
>
> This is a vote to release Apache Camel Quarkus 2.3.0.
>
> Highlights:
>
> * Quarkus 2.3.0.Final
> * Fixed issues:
> https://github.com/apache/camel-quarkus/milestone/19?closed=1
> * All
+1 (binding)
Thanks for the release, Zineb!
-- P
On 01/10/2021 21:55, Zineb Bendhiba wrote:
Hello,
This is a vote to release Apache Camel Quarkus 2.3.0.
Highlights:
* Quarkus 2.3.0.Final
* Fixed issues:
https://github.com/apache/camel-quarkus/milestone/19?closed=1
* All commits:
Hello,
This is a vote to release Apache Camel Quarkus 2.3.0.
Highlights:
* Quarkus 2.3.0.Final
* Fixed issues:
https://github.com/apache/camel-quarkus/milestone/19?closed=1
* All commits:
https://github.com/apache/camel-quarkus/compare/2.2.0...2.3.0
Staging repository:
I think it makes sense to go ahead with the release
Il gio 30 set 2021, 12:20 Claus Ibsen ha scritto:
> Hi
>
> I say we go ahead with the release.
>
> If it was a memory leak, CVE, or data corruption or some of that sorts
> in the core or important component,
> then a recut would be advised.
>
+1 (binding)
successfully tested with a spring-boot app
Am 29.09.2021 um 09:57 schrieb Gregor Zurowski:
Hi Everyone:
This is a vote to release Apache Camel 3.12.0, a new release with 206
new features and improvements.
Release notes:
+1 (non-binding)
Thanks!
Freeman
On Thu, Sep 30, 2021 at 4:18 AM Gregor Zurowski
wrote:
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.7.6 (with Apache Camel Spring
> Boot and Apache Camel Karaf), a new minor release with 15 improvements
> and fixes.
>
> This email contains the
Hello,
If we want to participate to Hacktoberfest we need to add labels to the
repository participating in this for the month of October.
Do we want to do this? Or do we prefer to avoid this and avoid all the
possible spam PRs arriving?
Let me know your thoughts.
Hi,
I find the shorter branch names a bit better (just because shorter is
better), as long as we do not release multiple independent projects from
the same git repo.
At the same time I would not mind to start using the longer branch names
ones if other Camel family members prefer them.
The
10 matches
Mail list logo