OK thanks.
Actually, I know cherry-pick -x / cherry-pick -e pretty well ;)
I’m using it for a while when back porting from main to activemq-5.xx.x
branches (and in bunch of others Apache projects) ;)
Regards
JB
> Le 15 janv. 2022 à 06:51, Clebert Suconic a écrit
> :
>
> I’m talking more
I’m talking more about a general point orthogonal to this discussion.
When you back port commits. If you used git cherry pick -x
I have a report to help track commits between branches.
On Fri, Jan 14, 2022 at 11:50 PM JB Onofré wrote:
> Hi Clebert
>
> We know but these point here was more
I’m glad it’s not a problem, thanks!
FWIW, I’d appreciate it if when there’s something that doesn’t follow the
“SHOULD” of an apache policy there’s an explanation of why: in this case the 48
hr rather than 72 hour voting window.
Thanks,
David Jencks
> On Jan 14, 2022, at 4:11 PM, Andrea
I noticed a few things working on the RI info for camel-kafka-connector.
- the compatibility matrices are thoroughly out of date, e.g.
https://camel.apache.org/camel-kafka-connector/0.11.0/user-guide/camel-compatibility-matrix.html
Hi Clebert
We know but these point here was more a discussion to the community if it makes
sense to remove the component in 5.16.x.
And actually it’s something we discussed in the original PR (I forgot): we
agreed to remove on for coming 5.17.x releases.
Regards
JB
> Le 14 janv. 2022 à
On Fri, Jan 14, 2022, at 22:00, David Jencks wrote:
> I don’t know if this makes any difference to anything, but I see that the
> camel-k-runtime version in ckc is 1.8.0, using kamelets 0.6.0, whereas in
> camel-k main it’s 1.10.0 using kamelets 0.5.0.
> (I’m looking at main rather than the
Yep I forgot to push it, here it is
https://github.com/apache/camel-kafka-connector/tree/camel-kafka-connector-1.0.x
got catch David Jencks
Thanks.
On Fri, Jan 14, 2022, at 21:56, Andrea Cosentino wrote:
> It could be created from main later, there shouldn't be new commits till
> the release
you guys should use cherry-pick -x between main and 5.16.x
then you could use this type of reporting I'm generating for between
main and 2.19.x on activemq artemis. it's fairly helpful I think.
easier to manage what's missing between the branches...
let me know if you need some help using
I don’t know if this makes any difference to anything, but I see that the
camel-k-runtime version in ckc is 1.8.0, using kamelets 0.6.0, whereas in
camel-k main it’s 1.10.0 using kamelets 0.5.0.
(I’m looking at main rather than the tag)
David Jencks
> On Jan 14, 2022, at 7:44 AM, Andrea
It could be created from main later, there shouldn't be new commits till
the release and if so we could branch from the tag.
I don't know if Andrea has the branch locally. Maybe he just forgot to push.
Il ven 14 gen 2022, 21:38 David Jencks ha
scritto:
> I see the tag, but no branch. Do you
I see the tag, but no branch. Do you usually create the branch after the vote
succeeds?
Thanks
David Jencks
> On Jan 14, 2022, at 7:44 AM, Andrea wrote:
>
> Hello all,
>
> This is a vote to release Apache Camel-kafka-connector 1.0.0
>
> Staging repository:
>
+1 (binding)
Thanks Andrea!
On Fri, Jan 14, 2022 at 4:44 PM Andrea wrote:
>
> Hello all,
>
> This is a vote to release Apache Camel-kafka-connector 1.0.0
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1399
>
> Tag:
>
+1 (binding)
Thanks Peter for cutting the release,
Alex
On Fri, Jan 14, 2022 at 1:23 PM James Netherton
wrote:
> +1 (binding)
>
> --
> James
>
> On Fri, 14 Jan 2022 at 09:33, Peter Palaga wrote:
>
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 2.2.1 - the first patch
> >
+1 (binding)
On Fri, Jan 14, 2022 at 4:44 PM Andrea wrote:
>
> Hello all,
>
> This is a vote to release Apache Camel-kafka-connector 1.0.0
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1399
>
> Tag:
>
+1 (non-binding)
Thanks Andrea!
On Fri, Jan 14, 2022 at 4:44 PM Andrea wrote:
> Hello all,
>
> This is a vote to release Apache Camel-kafka-connector 1.0.0
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1399
>
> Tag:
>
>
Hello all,
This is a vote to release Apache Camel-kafka-connector 1.0.0
Staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1399
Tag:
https://gitbox.apache.org/repos/asf?p=camel-kafka-connector.git;a=tag;h=refs/tags/camel-kafka-connector-1.0.0
based on camel
+1 (binding)
--
James
On Fri, 14 Jan 2022 at 09:33, Peter Palaga wrote:
> Hi,
>
> This is a vote to release Apache Camel Quarkus 2.2.1 - the first patch
> release of Camel Quarkus 2.2.x stream based on Camel 3.11.x LTS and
> Quarkus 2.2.x
>
> Highlights:
>
> * Camel 3.11.5
> * Quarkus
+1 (binding)
Thanks Peter!
zoran
On Fri, Jan 14, 2022 at 10:33 AM Peter Palaga wrote:
>
> Hi,
>
> This is a vote to release Apache Camel Quarkus 2.2.1 - the first patch
> release of Camel Quarkus 2.2.x stream based on Camel 3.11.x LTS and
> Quarkus 2.2.x
>
> Highlights:
>
> * Camel 3.11.5
> *
+1 (non binding)
Thanks Peter
Le ven. 14 janv. 2022 à 11:15, Jean-Baptiste Onofré a
écrit :
> +1 (binding)
>
> Regards
> JB
>
> On 14/01/2022 10:33, Peter Palaga wrote:
> > Hi,
> >
> > This is a vote to release Apache Camel Quarkus 2.2.1 - the first patch
> > release of Camel Quarkus 2.2.x
+1 (binding)
Regards
JB
On 14/01/2022 10:33, Peter Palaga wrote:
Hi,
This is a vote to release Apache Camel Quarkus 2.2.1 - the first patch
release of Camel Quarkus 2.2.x stream based on Camel 3.11.x LTS and
Quarkus 2.2.x
Highlights:
* Camel 3.11.5
* Quarkus 2.2.5.Final
* Log4j
+1 (binding)
On Fri, Jan 14, 2022 at 10:33 AM Peter Palaga wrote:
>
> Hi,
>
> This is a vote to release Apache Camel Quarkus 2.2.1 - the first patch
> release of Camel Quarkus 2.2.x stream based on Camel 3.11.x LTS and
> Quarkus 2.2.x
>
> Highlights:
>
> * Camel 3.11.5
> * Quarkus 2.2.5.Final
>
Hi,
This is a vote to release Apache Camel Quarkus 2.2.1 - the first patch
release of Camel Quarkus 2.2.x stream based on Camel 3.11.x LTS and
Quarkus 2.2.x
Highlights:
* Camel 3.11.5
* Quarkus 2.2.5.Final
* Log4j vulnerability fixes
* All commits:
22 matches
Mail list logo
