Proposing the (second) test build of Cassandra 4.1.0 for release.
sha1: f9e033f519c14596da4dc954875756a69aea4e78
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.1.0-tentative
Maven Artifacts:
Sure
> On 7 Dec 2022, at 20:47, Mick Semb Wever wrote:
>
>
>
>> Can we give Marianne and Matt a chance to confirm their performance numbers?
>> I got an indicative message suggesting it looked good, but nothing firm yet.
>
>
>
> I am presuming that will (and must) happen before the new
> Can we give Marianne and Matt a chance to confirm their performance
> numbers? I got an indicative message suggesting it looked good, but nothing
> firm yet.
>
I am presuming that will (and must) happen before the new vote closes
(which will be next Monday anyway). I don't see much point in
Can we give Marianne and Matt a chance to confirm their performance numbers? I
got an indicative message suggesting it looked good, but nothing firm yet.
> On 7 Dec 2022, at 20:37, Mick Semb Wever wrote:
>
>
>
>> The vote will be open for 72 hours (longer if needed). Everyone who has
>>
> 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.
>
This vote failed due to CASSANDRA-18086, which has now been
Dear community,
I have created the epic with code-style activities to track the progress:
https://issues.apache.org/jira/browse/CASSANDRA-18090
In my understanding, there is no need to format whole the code base at
once according to the code style described on the page [1], and the
best
>
> I think it makes sense to look into improving visibility of API changes,
> so people can more easily review a summary of API changes versus reading
> through the whole changelog (perhaps we need a summarized API change log?).
>
Agree Paulo.
Observers should be able to see all API changes
The comparator for collections is the lexicographical compare on the
collection items. That might nor be the more useful thing but it's not
impossible to imagine cases where that ordering can be useful. To make a
random example, you can use a list column to store the name and surnames of
a person,
>
> Given that we're talking about two one-liners, just changing time units,
> what are folks thoughts about skipping rc2 and just re-cutting 4.1.0 (GA) ?
It sounds reasonable to me.
Le mar. 6 déc. 2022 à 22:36, Aleksey Yeshchenko a
écrit :
> Sure.
>
> On 6 Dec 2022, at 18:14, Mick Semb Wever
