+1!
/Marcus
On Fri, Nov 24, 2023 at 04:43:36PM +0100, Alex Petrov wrote:
> Hi everyone,
>
> With TCM landed, there will be way more Harry tests in-tree: we are using it
> for many coordination tests, and there's now a simulator test that uses
> Harry. During development, Harry has allowed us
Welcome!
On 29/11/23 2:24, guo Maxwell wrote:
Congrats!
Jacek Lewandowski 于2023年11月29日周三
06:16写道：
Congrats!!!
wt., 28 lis 2023, 23:08 użytkownik Abe Ratnofsky
napisał:
Congrats Francisco!
> On Nov 28, 2023, at 1:56 PM, C. Scott Andreas
wrote:
I hate to say it, but I was disappointed that this email thread was started
after the TCM work had already been committed. Especially knowing how we
had even an epic with patches spread around the codebase, which are waiting
on TCM to get committed first so that we do not disturb any rebase. The
Congrats!
Jacek Lewandowski 于2023年11月29日周三 06:16写道：
> Congrats!!!
>
> wt., 28 lis 2023, 23:08 użytkownik Abe Ratnofsky napisał:
>
>> Congrats Francisco!
>>
>> > On Nov 28, 2023, at 1:56 PM, C. Scott Andreas
>> wrote:
>> >
>> > Congratulations, Francisco!
>> >
>> > - Scott
>> >
>> >> On Nov
+1 from me
> On Nov 28, 2023, at 12:55 PM, Doug Rohrer wrote:
>
> +1 (nb, but not a vote, so ¯\_(ツ)_/¯ ) - would be lovely to not have to deal
> with this individually for each project in which we use the in-jvm dtest
> framework. As Francisco noted, we’re using this in the sidecar and
Congrats!!!
wt., 28 lis 2023, 23:08 użytkownik Abe Ratnofsky napisał:
> Congrats Francisco!
>
> > On Nov 28, 2023, at 1:56 PM, C. Scott Andreas
> wrote:
> >
> > Congratulations, Francisco!
> >
> > - Scott
> >
> >> On Nov 28, 2023, at 10:53 AM, Dinesh Joshi wrote:
> >>
> >> The PMC members
So then cutting an alpha2 is possible.
>
Possible, but still leaves alpha1 as our mitigation plan and alpha2 as our
best plan. Doesn't seem worth it IMHO.
So then cutting an alpha2 is possible.
Kind Regards,
Brandon
On Tue, Nov 28, 2023 at 2:59 PM Mick Semb Wever wrote:
>
>
> You can't change bits in a signed and checksummed artefact. You have to cut
> from scratch.
>
> On Tue, 28 Nov 2023 at 20:28, Brandon Williams wrote:
>>
>> I think the
You can't change bits in a signed and checksummed artefact. You have to
cut from scratch.
On Tue, 28 Nov 2023 at 20:28, Brandon Williams wrote:
> I think the last time I looked into it there was nothing in the
> scripts that forced anything, but if that's not true I think we should
> be fixing
+1 (nb, but not a vote, so ¯\_(ツ)_/¯ ) - would be lovely to not have to deal
with this individually for each project in which we use the in-jvm dtest
framework. As Francisco noted, we’re using this in the sidecar and Analytics
projects now and I’ve had to jump through a lot of hoops to get
Thanks everyone! I'm happy to be part of the Cassandra community, now as a
committer. Thanks again to everyone who has helped me onboard in the project
and for the guidance navigating in the project.
I'm looking forward to working with you.
Best,
- Francisco
On 2023/11/28 19:56:09 Arjun Ashok
Congrats Francisco!
On Tue, Nov 28, 2023 at 10:54 AM Dinesh Joshi wrote:
> The PMC members are pleased to announce that Francisco Guerrero Hernandez
> has accepted
> the invitation to become committer today.
>
> Congratulations and welcome!
>
> The Apache Cassandra PMC members
--
Arjun
Congrats Francisco!
> On 28 Nov 2023, at 18:52, Dinesh Joshi wrote:
>
> The PMC members are pleased to announce that Francisco Guerrero Hernandez has
> accepted
> the invitation to become committer today.
>
> Congratulations and welcome!
>
> The Apache Cassandra PMC members
Congrats Francisco!
On Tue, Nov 28, 2023, at 2:37 PM, Melissa Logan wrote:
> Congrats Francisco!
>
> On Tue, Nov 28, 2023 at 11:34 AM Vinay Chella wrote:
>> Congratulations Francisco !!
>>
>> Thanks,
>> Vinay Chella
>>
>>
>> On Tue, Nov 28, 2023 at 11:24 AM Mick Semb Wever wrote:
>>>
>>>
Building these jars every time we run every CI job is just silly.
+1.
On Tue, Nov 28, 2023, at 2:08 PM, Francisco Guerrero wrote:
> Hi Abe,
>
> I'm +1 on this. Several Cassandra-ecosystem projects build the dtest jar in
> CI. We'd very
> much prefer to just consumed shaded dtest jars from
Congrats Francisco!
On Tue, Nov 28, 2023 at 11:34 AM Vinay Chella
wrote:
> Congratulations Francisco !!
>
> Thanks,
> Vinay Chella
>
>
> On Tue, Nov 28, 2023 at 11:24 AM Mick Semb Wever wrote:
>
>>
>>
>> On Tue, 28 Nov 2023 at 19:54, Dinesh Joshi wrote:
>>
>>> The PMC members are pleased to
Congratulations Francisco !!
Thanks,
Vinay Chella
On Tue, Nov 28, 2023 at 11:24 AM Mick Semb Wever wrote:
>
>
> On Tue, 28 Nov 2023 at 19:54, Dinesh Joshi wrote:
>
>> The PMC members are pleased to announce that Francisco Guerrero Hernandez
>> has accepted
>> the invitation to become
I think the last time I looked into it there was nothing in the
scripts that forced anything, but if that's not true I think we should
be fixing that, not having it drive our release decisions.
Kind Regards,
Brandon
On Tue, Nov 28, 2023 at 12:54 PM Mick Semb Wever wrote:
>
>
>
> On Tue, 28 Nov
Hi Maxim,
I'm part of the K8ssandra team and am very happy to hear that you like our
management API design.
Looking at the CEP, I see that your current target design mentions the
k8ssandra-management-api.
What do you have in mind specifically there? Do you plan on rewriting a
brand new
On Tue, 28 Nov 2023 at 19:54, Dinesh Joshi wrote:
> The PMC members are pleased to announce that Francisco Guerrero Hernandez
> has accepted
> the invitation to become committer today.
>
> Congratulations and welcome!
Congrats !!
Congrats Francisco!
Kind Regards,
Brandon
On Tue, Nov 28, 2023 at 12:53 PM Dinesh Joshi wrote:
>
> The PMC members are pleased to announce that Francisco Guerrero Hernandez has
> accepted
> the invitation to become committer today.
>
> Congratulations and welcome!
>
> The Apache Cassandra PMC
Congratulations Francisco!
On Tue, Nov 28, 2023 at 11:10 AM Ekaterina Dimitrova
wrote:
> Congrats Francisco! Well deserved !
>
> On Tue, 28 Nov 2023 at 14:08, J. D. Jordan
> wrote:
>
>> Congrats!
>>
>> > On Nov 28, 2023, at 12:57 PM, C. Scott Andreas
>> wrote:
>> >
>> > Congratulations,
Congrats Francisco! Well deserved !
On Tue, 28 Nov 2023 at 14:08, J. D. Jordan
wrote:
> Congrats!
>
> > On Nov 28, 2023, at 12:57 PM, C. Scott Andreas
> wrote:
> >
> > Congratulations, Francisco!
> >
> > - Scott
> >
> >> On Nov 28, 2023, at 10:53 AM, Dinesh Joshi wrote:
> >>
> >> The PMC
Hi Abe,
I'm +1 on this. Several Cassandra-ecosystem projects build the dtest jar in CI.
We'd very
much prefer to just consumed shaded dtest jars from Cassandra releases for
testing
purposes.
Best,
- Francisco
On 2023/11/28 19:02:17 Abe Ratnofsky wrote:
> Hey folks - wanted to raise a separate
“The QA label is part of our version number and that's baked in.”
How can we have beta 2, but there is no way for alpha 2?
On Tue, 28 Nov 2023 at 13:55, Mick Semb Wever wrote:
>
>
> On Tue, 28 Nov 2023 at 19:27, J. D. Jordan
> wrote:
>
>> That said. This is clearly better than and with many
Congrats!
> On Nov 28, 2023, at 12:57 PM, C. Scott Andreas wrote:
>
> Congratulations, Francisco!
>
> - Scott
>
>> On Nov 28, 2023, at 10:53 AM, Dinesh Joshi wrote:
>>
>> The PMC members are pleased to announce that Francisco Guerrero Hernandez
>> has accepted
>> the invitation to become
Congratulations! It is well deserved.
发件人: C. Scott Andreas
发送时间: Wednesday, November 29, 2023 2:56:34 AM
收件人: dev@cassandra.apache.org
主题: Re: Welcome Francisco Guerrero Hernandez as Cassandra Committer
Congratulations, Francisco!
- Scott
> On Nov 28, 2023,
Hey folks - wanted to raise a separate thread to discuss publishing of
dtest-shaded JARs on release.
Currently, adjacent projects that want to use the jvm-dtest framework need to
build the shaded JARs themselves. This is a decent amount of work, and is
duplicated across each project. This is
Congrats Francisco!
> On Nov 28, 2023, at 1:56 PM, C. Scott Andreas wrote:
>
> Congratulations, Francisco!
>
> - Scott
>
>> On Nov 28, 2023, at 10:53 AM, Dinesh Joshi wrote:
>>
>> The PMC members are pleased to announce that Francisco Guerrero Hernandez
>> has accepted
>> the invitation
Congratulations, Francisco!
- Scott
> On Nov 28, 2023, at 10:53 AM, Dinesh Joshi wrote:
>
> The PMC members are pleased to announce that Francisco Guerrero Hernandez
> has accepted
> the invitation to become committer today.
>
> Congratulations and welcome!
>
> The Apache Cassandra PMC
Another strong +1 to have Harry in-tree, and another +1 to building shaded
dtest JARs on release. There are a number of projects that would benefit from
having these JARs available in a central repository, like Sidecar, Driver, etc.
I didn't see a ticket so created one:
On Tue, 28 Nov 2023 at 19:27, J. D. Jordan
wrote:
> That said. This is clearly better than and with many fixes from the alpha.
> Would people be more comfortable if this cut was released as another alpha
> and we do beta1 once the known fixes land?
>
There is no way with our release process to
The PMC members are pleased to announce that Francisco Guerrero Hernandez has
accepted
the invitation to become committer today.
Congratulations and welcome!
The Apache Cassandra PMC members
If the consensus is that meaningful community testing will occur in the
week between "beta1 but SAI is broken, friends" and "ok, beta2, it's fixed
now, go for it"...then go for it.
On Tue, Nov 28, 2023 at 12:40 PM Patrick McFadin wrote:
> JD, that wasn't my point. It feels like we are treating
-0 to cutting a beta we know has a very obvious correctness flaw with a fix
already understood
On Tue, Nov 28, 2023 at 10:40 AM Patrick McFadin wrote:
> JD, that wasn't my point. It feels like we are treating a beta like an RC,
> which it isn't. Ship Beta 1 now and Beta 2 later. We need
JD, that wasn't my point. It feels like we are treating a beta like an RC,
which it isn't. Ship Beta 1 now and Beta 2 later. We need people looking
today because they will find new bugs and the signal is lost on alpha. It's
too yolo for most people.
On Tue, Nov 28, 2023 at 10:36 AM Benjamin Lerer
I'm fine w/ alpha2 now and beta1 once we resolve 19011.
On Tue, Nov 28, 2023 at 12:36 PM Benjamin Lerer wrote:
> -1 based on the problems raised by Caleb.
>
> I would be fine with releasing that version as an alpha as Jeremiah
> proposed.
>
> As of this time, I'm also not aware of a user of the
-1 based on the problems raised by Caleb.
I would be fine with releasing that version as an alpha as Jeremiah
proposed.
As of this time, I'm also not aware of a user of the project operating a
> build from the 5.0 branch at substantial scale to suss out the operational
> side of what can be
That said. This is clearly better than and with many fixes from the alpha. Would people be more comfortable if this cut was released as another alpha and we do beta1 once the known fixes land?On Nov 28, 2023, at 12:21 PM, J. D. Jordan wrote:-0 (NB) on this cut. Given the concerns expressed so
-0 (NB) on this cut. Given the concerns expressed so far in the thread I would think we should re-cut beta1 at the end of the week.On Nov 28, 2023, at 12:06 PM, Patrick McFadin wrote:I'm a +1 on a beta now vs maybe later. Beta doesn't imply perfect especially if there are declared known issues.
I'm a +1 on a beta now vs maybe later. Beta doesn't imply perfect
especially if there are declared known issues. We need people outside of
this tight group using it and finding issues. I know how this rolls. Very
few people touch a Alpha release. Beta is when the engine starts and we
need to get
>
> The vote will be open for 72 hours (longer if needed). Everyone who has
> tested the build is invited to vote. Votes by PMC members are considered
> binding. A vote passes if there are at least three binding +1s and no -1's.
>
+1
Checked
- signing correct
- checksums are correct
- source
>
> Compared to the rigor of our previous major release, this feels rushed and
> timeline-driven rather than anchored in values of quality and data
> integrity.
>
Yes, it is (unfortunately) time-driven. But rather than say rushed I would
say incremental.
At the Summit, whatever release we end
Agreed with Brandon, yes. I'm at a "-0 (nb)" on a beta release at this point. We're clearly finding (and
resolving) lots of significant and in some case serious issues - ones that violate fundamental properties of the
database. I'm very glad that we're finding and fixing these, but they feel
If we are going to commit to beta2 before the summit because "putting
a beta w/ SAI in this state into users’ hands at summit would be very,
very bad" I don't see why we need to have a subpar beta1 at all?
Kind Regards,
Brandon
On Tue, Nov 28, 2023 at 11:16 AM Mick Semb Wever wrote:
>
>
>
> On
On Tue, 28 Nov 2023 at 18:06, Caleb Rackliffe
wrote:
> Just to update this thread, Mike has identified the root cause of 19011
> and in the process uncovered 2 additional very closely related issues.
> (Fantastic job fuzzing there!) Fixes for all three issues are in hand, and
> he continues to
Just to update this thread, Mike has identified the root cause of 19011 and in the process uncovered 2 additional very closely related issues. (Fantastic job fuzzing there!) Fixes for all three issues are in hand, and he continues to test.After some conversation w/ Mick, Alex, and Mike, I feel
Should I assume it's an agreement?
- - -- --- - -
Jacek Lewandowski
wt., 28 lis 2023 o 12:05 Mick Semb Wever napisał(a):
>
>
> So, assuming beta2, can it be merged to cassandra-5.0 now?
>>
>
>
> Yes from me.
> And I would interpret Brandon and Maxwell's statements as
So, assuming beta2, can it be merged to cassandra-5.0 now?
>
Yes from me.
And I would interpret Brandon and Maxwell's statements as supporting too.
So, assuming beta2, can it be merged to cassandra-5.0 now?
- - -- --- - -
Jacek Lewandowski
pon., 27 lis 2023 o 16:02 Mick Semb Wever napisał(a):
>
> I don't want to veto the 5.0-beta1 release for this.
>
> I would rather cut and include it in the next: 5.0-beta2;
Sure, that should be possible. I will check and will get back.
On Mon, Nov 27, 2023, at 10:10 PM, Ekaterina Dimitrova wrote:
> +1, also, Alex, just an idea - maybe you want to make a virtual talk, as part
> of the contributors meetings?
>
>
> На понеделник, 27 ноември 2023 г. Yifan Cai
51 matches
Mail list logo
