>
> 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.
>
Vote passes.
Five +1 binding.
Two +1 non-binding.
One +0 non-bind
>
> 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.
>
Vote passes.
Four +1 binding.
One +1 non-binding.
Two -1 non-bind
>
> 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.
>
Vote passes.
Four +1 binding.
One +1 non-binding.
Two -1 non-bindi
Hi,
Just a heads up that I created CASSANDRA-17372 to explore supporting
dynamic table TTL and would like to hear your feedback (on the idea) before
moving forward with a design. Please add any potential comments to the
ticket.
Cheers,
Paulo
[1] - https://issues.apache.org/jira/browse/CASSANDRA
CI results:
https://ci-cassandra.apache.org/job/Cassandra-3.0/245/
https://nightlies.apache.org/cassandra/ci-cassandra.apache.org/job/Cassandra-3.0/245/
https://nightlies.apache.org/cassandra/Cassandra-3.0/245/
> I'd be interested to hear from Mike/Jason on the OR support topic, of course.
The support for OR within SAI is fairly minimal and will not work without the
non-SAI changes needed. Since the non-SAI OR changes are extensive it would be
better to bring those in under their own CEP.
I’d leave t
+1 on the release
On Thu, Feb 10, 2022 at 7:23 AM Ekaterina Dimitrova
wrote:
> +0nb
> I am not sure I am getting enough information from our CI to vote for
> either +1 or -1. I was chasing CI issues two days, being worried did I
> break something with CCM change I introduced over the weekend as
+0nb
I am not sure I am getting enough information from our CI to vote for
either +1 or -1. I was chasing CI issues two days, being worried did I
break something with CCM change I introduced over the weekend as CI started
hanging in a weird way. (If I knew there will be a release I wouldn’t have
co
Let us continue the configuration discussion in the CEP-11 JIRA (
https://issues.apache.org/jira/browse/CASSANDRA-17034).
Any further comments on the alternate memtable? Are we ready for a vote?
Regards,
Branimir
On Wed, Feb 9, 2022 at 12:13 PM Bowen Song wrote:
> TBH, I don't have an opinion
CI results:
https://ci-cassandra.apache.org/job/Cassandra-3.0/245/
https://nightlies.apache.org/cassandra/ci-cassandra.apache.org/job/Cassandra-3.0/245/
https://nightlies.apache.org/cassandra/Cassandra-3.0/245/
+1 nb
On Mon, 2022-02-07 at 15:14 +0100, Mick Semb Wever wrote:
Proposing the test build of Cassandra 3.11.12 for release.
sha1: b44ff92eb2921e8d66fe2e994cb27289d3786faa
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.12-tentative
Maven Artifacts:
https://
+1 nb
On Mon, 2022-02-07 at 15:14 +0100, Mick Semb Wever wrote:
Proposing the test build of Cassandra 4.0.2 for release.
sha1: 25012d2fec1984cc9c1a352f214eb912ca4f10f5
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.2-tentative
Maven Artifacts:
https://repo
CI Results:
https://ci-cassandra.apache.org/job/Cassandra-3.11/318/
https://nightlies.apache.org/cassandra/ci-cassandra.apache.org/job/Cassandra-3.11/318/index.html
https://nightlies.apache.org/cassandra/Cassandra-3.11/318/
>
> Where we said:
> "All releases by default are expected to have a green test run on
> ci-cassandra.apache.org Jenkins. In exceptional circumstances (security
> incidents, data loss, etc requiring hotfix), members with binding votes
> on a release may choose to approve a release with known failin
14 matches
Mail list logo
