Jumping in, I'm ok to allow it in tests for a trial period too. I would
imagine in test methods especially it's of much less concern, where the
code is much simpler to read, and also safer to change to types later on.
On Wed, 8 Jan 2025 at 16:46, Josh McKenzie wrote:
> I would like to remove th
datastax-labs/hunter is now transferred to apache/hunter
if the new name is confirmed, create another infra ticket to rename it
again.
On Wed, 4 Dec 2024 at 18:02, Lari Hotari wrote:
> +1 for INFRA-26336 change.
> I support the renaming from `apache/incubator-hunter` to `apache/hunter`.
>
> -L
alified name,
>> > > could
>> > > > be good to check as well.
>> > > >
>> > > >
>> > > > Even so, from the above list I actually like Apache Otava.
>> Personally I
>> > > > never felt l
On Mon, 16 Dec 2024 at 02:16, Henrik Ingo wrote:
> Mick was asking for a name that somehow is associated with the topic of
> change detection. I feel like Karen and Suunnistus are perhaps not quite
> what you asked for?
I'm not asking for anything. Was only contributing to ideas (open mode).
On Fri, 13 Dec 2024 at 06:06, Jeremiah Jordan
wrote:
> TL;DR - in progress migration off 2.2 to 5.0 is annoying as there were
>>> different bugs in the past we have to support again. Out of process
>>> migration to me feels far more plausible, but feels annoying without
>>> splitting off our rea
I know a few teams on 2.2 that would *love* to be able to jump right to
> 5.0. Once you fall far enough behind, upgrading to another version that's
> already deprecated becomes paralyzing. I don't expect 2.2 compatibility
> btw, just using it as an example.
>
> If it can be done, it would make a
I'm still looking/waiting for the rationale for this decision.
On Wed, 11 Dec 2024 at 08:31, Dave Fisher wrote:
>
> Hi -
>
> You may have seen on PODLINGNAMESEARCH-228 and the Incubator list that Apache
> Hunter as a brand is not approved.
>
> The podling will need to find a new name, better soo
I would very much rather keep our upgrade paths simple and intuitive:
You can only upgrade between adjacent major versions.
This does catch users, and keeping it simple has helped a lot.
I find it helps internally working on the code too, with a focus on
stability for online upgrades, which does q
On Tue, 10 Dec 2024 at 22:42, Henrik Ingo wrote:
> On Mon, Dec 9, 2024 at 5:24 PM Sean McCarthy
> wrote:
>
> > I believe datastax-labs/hunter is being moved into apache/hunter by
> > ASF-infra, according to: https://issues.apache.org/jira/browse/HUNTER-1
> <
> > https://issues.apache.org/jira/br
> A possibility with SAI is to mark it beta while also marking 2i as
> deprecated (and leaving SASI as marked). This sends a clear signal
> (imho) that SAI is the recommended solution forward but also being
> honest about its maturity and QA.
(and leaving SASI as marked *experimental*)
I see value in using a beta flag in addition to an experimental flag,
and that such a beta flag should see a lot more use than experimental.
Java 17 definitely falls in the beta category. I/We definitely
recommend its usage in production, but as has been said data is needed
over trust and the co
Chiming in with my two cents…
When people have the luxury of working in environments where clusters are
> massively over provisioned, LCS as a default makes a lot of sense, because
> there's not much downside. The use cases where you'd actually fall behind
> in compaction are pretty slim, so the
>
> Besides the site framework, we also need to decide whether we want to keep
> the website as part of the main repository in a folder or branch, or have
> it in an independent repository. I recommend creating a separate repository
> for the website so that we don't increase the size of the main r
+1 for more code (github/ide) readable in-code documentation.
Do we use javadoc anywhere anymore, or read its generated apidocs
anywhere ? We removed that target from the build cycle, and don't
publish those artefacts or deploy the apidocs anywhere anymore… I
would say folk are either got the c
> I'm kicking off the formal vote to accept Hunter into the ASF Incubator.
>
>
> Please cast your vote:
> [ ] +1, accept Hunter into the ASF Incubator
> [ ] 0, I don't care either way
> [ ] -1, do not accept Hunter into the ASF Incubator, because ...
With 21 +1 votes ( 11 binding and 10 non-bind
+1 – mck ipmc
On Fri, 22 Nov 2024 at 03:31, Craig Russell wrote:
> +1 clr (IPMC)
>
> > On Nov 21, 2024, at 04:15, Mick Semb Wever wrote:
> >
> > Following the discussion about Hunter started ten days ago
> > https://lists.apache.org/thread/ojr23ssmxmfsdb
Following the discussion about Hunter started ten days ago
https://lists.apache.org/thread/ojr23ssmxmfsdbnojxg3q02xdl74t75j
and its proposal
https://cwiki.apache.org/confluence/display/INCUBATOR/HunterProposal
I'm kicking off the formal vote to accept Hunter into the ASF Incubator.
Please ca
On Sat, 16 Nov 2024 at 00:18, Caleb Rackliffe
wrote:
> The subject line probably says it all, but just to confirm, we won't be
> supporting 3.11 -> 5.1/trunk upgrades, correct?
>
Correct. To be specific, online upgrades.
> If that's correct, I'm going to go ahead and remove v30 and v3X from
>
>
> 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
- sourc
Hi Apache Incubator folks,
Proposing a new project: Hunter.
Hunter is a tool that detects statistically significant changes in
time-series data stored either in databases or CSV files. It is designed to
be easily integrated into build pipelines and provide automated performance
analysis that can
As per the CEP process documentation, this vote will be open for 72 hours
> (longer if needed).
>
+1
Can you please put the ticket description in the email. Saves us having to
follow the link to know what you're talking about.
Yes to backporting this.
On Tue, 5 Nov 2024 at 10:27, Štefan Miklošovič
wrote:
> Hello,
>
> I want to ask if there are objections for backporting CASSANDRA-17812 (1)
>
Thanks Jaydeep. I've exhausted my lines on enquiry and am happy that
thought has gone into them.
> On top of the above list, here is my recommendation (this is just a pure
> thought only and subject to change depending on how all the community
> members see it):
>
>- Nov-Dec: We can definit
Jaydeep,
your replies address my main concerns, there's a few questions of
curiosity as replies inline below…
> >Without any per-table scheduling and history (IIUC) a node would have
> to restart the repairs for all keyspaces and tables.
>
> The above-mentioned quote should work fine and wi
any name works for me, Jaydeep :-)
I've taken a run through of the CEP, design doc, and current PR. Below are
my four (rough categories of) questions.
I am keen to see a MVP land, so I'm more looking at what the CEP's design
might not be able to do, rather than what may or may not land in an init
On Wed, 23 Oct 2024 at 05:48, Jordan West wrote:
> Josh/Mick, where does that leave us? I’d like to start with the smaller
> scope Josh described in his last email. We can tackle in-tree/stress
> separately.
>
> I was going to start working on getting signed ICLAs. Does that still
> sound like th
The Cassandra team is pleased to announce the release of Apache Cassandra
version 5.0.2.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source an
The Cassandra team is pleased to announce the release of Apache Cassandra
version 5.0.2.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source an
>
> Isn't it weird that you said that we should not save characters at the
> cost of readability while we just use CASS everywhere except the main
> project? Why do you think that having "CASS-" will make people
> automatically think that this is Cassandra related. No other project in
> Apache (afa
Vote passes with six +1s (four binding) and no vetoes.
ref: https://lists.apache.org/thread/wb8k7t0vfpj5hs4k7h2gydbkl8qmlsqz
On Wed, 16 Oct 2024 at 14:18, Mick Semb Wever wrote:
> Proposing the test build of Cassandra 5.0.2 for release.
>
> sha1: f278f6774fc76465c182041e081982105c3e7
This is looking strong, thanks Jaydeep.
I would suggest folk take a look at the design doc and the PR in the CEP.
A lot is there (that I have completely missed).
I would especially ask all authors of prior art (Reaper, DSE nodesync,
ecchronos) to take a final review of the proposal
Jaydeep, can
;> >>> Kind Regards,
>>>>> > >> >>> Brandon
>>>>> > >> >>>
>>>>> > >> >>> On Wed, Oct 2, 2024 at 5:07 PM Brandon Williams <
>>>>> dri...@gmail.com>
>>&g
reply below.
> 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 correct
- s
Proposing the test build of Cassandra 5.0.2 for release.
sha1: f278f6774fc76465c182041e081982105c3e7dbb
Git: https://github.com/apache/cassandra/tree/5.0.2-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1349/org/apache/cassandra/cassandra-all/5.0.2
arg parsing alone is a
> 5K line mess. It's certainly not being well-maintained and could use a
> replacement.
>
> On Sun, Oct 13, 2024 at 10:25 PM Josh McKenzie
> wrote:
>
>
> Unsolicited .02:
>
> - If this will eventually replace the in-tree cassandra-stress, does i
The test build of Cassandra 5.0.2 is available.
sha1: f278f6774fc76465c182041e081982105c3e7dbb
Git: https://github.com/apache/cassandra/tree/5.0.2-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1349/org/apache/cassandra/cassandra-all/5.0.2/
The So
I'll start a 5.0.2 release then…
unless there's anything else in-flight I should be waiting for …?
On Fri, 11 Oct 2024 at 23:06, Caleb Rackliffe
wrote:
> Just to close the loop, this is committed to 5.0 and trunk.
>
> On Wed, Oct 9, 2024 at 3:07 PM Caleb Rackliffe
> wrote:
>
>> Hey folks,
>>
reply below.
> I’m terms of next steps: Mick what do we need to do next? Figure out the
> answers to your questions re: getting contributor sign off?
>
The process of donation is as follows… (feel free to correct me, or add
anything)
1. General pre-agreement from the PMC that we'll take this
To play devil's advocate here, it's important that the subprojects don't
lose visibility and silo from the rest of the project.
There are different ways to solve this, and lumping everything into one
jira project is a messy and poor way of doing it. But as the sidecar has
shown us, subproject act
The Cassandra team is pleased to announce the release of Apache Cassandra
version 5.0.1.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source an
The Cassandra team is pleased to announce the release of Apache Cassandra
version 5.0.1.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source an
Agree with Jon, Josh and Patrick here.
This is the type of hidden subproject that will get us into trouble with
the board/foundation. I'm sure it's getting enough committer eyeballs,
and some PMC oversight, but maybe not enough. Addressing the more material
points that Jon mentions is the best
.
Proposing the test build of Cassandra 5.0.1 for release.
>
> sha1: c206e4509003ac4cd99147d821bd4b5d23bdf5e8
> Git: https://github.com/apache/cassandra/tree/5.0.1-tentative
> Maven Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1348/org/apache/cassandra/cassand
The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.1.7.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source an
The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.1.7.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source an
The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.0.14.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.0.14.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
Vote passes with five +1s, four binding.
ref: https://lists.apache.org/thread/clq6959ntgltbpzx21xl1jkphcowwgg7
On Fri, 20 Sept 2024 at 16:35, Mick Semb Wever wrote:
>
> Proposing the test build of Cassandra 4.1.7 for release.
>
> sha1: ca494526025a480bc8530ed3ae472ce8c9cbaf7a
Vote passes with three binding +1s
ref: https://lists.apache.org/thread/lps6bskc1lr8f5bfhglystcmjdnqzn24
On Fri, 20 Sept 2024 at 16:35, Mick Semb Wever wrote:
>
> Proposing the test build of Cassandra 4.0.14 for release.
>
> sha1: 7bf67349579411521bcdee4febd209cff63179a6
.
>
> The vote will be open for 96 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 correct
- source ar
.
>
> The vote will be open for 96 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
- sour
.
>
> The vote will be open for 96 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
Proposing the test build of Cassandra 5.0.1 for release.
sha1: c206e4509003ac4cd99147d821bd4b5d23bdf5e8
Git: https://github.com/apache/cassandra/tree/5.0.1-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1348/org/apache/cassandra/cassandra-all/5.0.1
Proposing the test build of Cassandra 4.1.7 for release.
sha1: ca494526025a480bc8530ed3ae472ce8c9cbaf7a
Git: https://github.com/apache/cassandra/tree/4.1.7-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1347/org/apache/cassandra/cassandra-all/4.1.7
Proposing the test build of Cassandra 4.0.14 for release.
sha1: 7bf67349579411521bcdee4febd209cff63179a6
Git: https://github.com/apache/cassandra/tree/4.0.14-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1345/org/apache/cassandra/cassandra-all/4.0
The test builds of Cassandra 4.0.14, 4.1.7 and 5.0.1, are available.
A vote of this test build will be initiated within the next couple of days.
== 4.0.14 ==
sha1: 7bf67349579411521bcdee4febd209cff63179a6
Git: https://github.com/apache/cassandra/tree/4.0.14-tentative
Maven Artifacts:
https://repo
reply below.
> Mick - this patch doesn't fix things 100%. It can't. BUT - it does take us
> from "In all cases where this occurs you will silently lose data" to "in
> some cases where this occurs you will have a rejected write, in others
> you'll have coordinator level logging, and in the worst
replies below (to Scott, Josh and Jeremiah).
tl;dr all my four points remain undisputed, when the patch is applied.
This is a messy situation, but no denying the value of rejection writes to
various known popular scenarios. Point (1) remains important to highlight
IMHO.
On Fri, 13 Sept 2024 at
es then the nodes may as well be down.
> Unless the end user is writing at CL ANY they have requested to be ACKed
> when CL nodes which own the data have acked getting it.
>
> -Jeremiah
>
> On Sep 12, 2024 at 2:35:01 PM, Mick Semb Wever wrote:
>
>> Great that the discus
reply below
On Thu, 12 Sept 2024 at 21:56, Josh McKenzie wrote:
> I'd like to propose we treat all data loss bugs as "fix by default on all
> supported branches even if that might introduce user-facing changes".
>
> Even if only N of M people on a thread have experienced it.
> Even if we only un
Yes, and my usage of CL.*ONE wasn't so correct (as writes are
backgrounded), but…
The point is we should be accurate and precise in talking about this (folk
will come back and read this thread), both in how it can manifest, the
limitations of both logging and rejection, what possible remedies are,
will be lost than silently lose it.
>
> Of course, a change like this requires very good communication in NEWS.txt
> and elsewhere but I think its well worth it. While it may surprise some
> users I think they would be more surprised that they were silently losing
> data.
>
> Jord
Thanks for starting the thread Caleb, it is a big and impacting patch.
Appreciate the criticality, in a new major release rejection by default is
obvious. Otherwise the logging and metrics is an important addition to
help users validate the existence and degree of any problem.
Also worth mentio
The PMC's members are pleased to announce that Chris Bannister, James
Hartig, Jackson Flemming and João Reis have accepted invitations to become
committers on the Drivers subproject.
Thanks a lot for everything you have done with the gocql driver all these
years. We are very excited to see the dr
>
> The vote will be open for 24 hours. 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.
>
+1
The Cassandra team is pleased to announce the GA release of Apache
Cassandra version 5.0.0.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source
Vote passes with three binding +1 votes.
ref: https://lists.apache.org/thread/b568cx8l1y2tx93rrc9fnhsohg3jqzk6
On Mon, 2 Sept 2024 at 12:11, Mick Semb Wever wrote:
>
> Proposing the test build of Cassandra 5.0.0 for release.
>
> sha1: 186272edca920c757b91bf95c2392bafa1a38d72
.
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 correct
- source artefa
Proposing the test build of Cassandra 5.0.0 for release.
sha1: 186272edca920c757b91bf95c2392bafa1a38d72
Git: https://github.com/apache/cassandra/tree/5.0.0-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1342/org/apache/cassandra/cassandra-all/5.0.0
The test build of Cassandra 5.0.0 GA is available.
sha1: 186272edca920c757b91bf95c2392bafa1a38d72
Git: https://github.com/apache/cassandra/tree/5.0.0-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1342/org/apache/cassandra/cassandra-all/5.0.0/
The
The Cassandra team is pleased to announce the release of Apache Cassandra
version 5.0-rc2.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source
The Cassandra team is pleased to announce the release of Apache Cassandra
version 5.0-rc2.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source
.
> Proposing the test build of Cassandra 5.0-rc2 for release.
> …
> 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.
>
.
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 correct
- source artef
Proposing the test build of Cassandra 5.0-rc2 for release.
sha1: 06691fce25a215361332aa1767e188bb6694687a
Git: https://github.com/apache/cassandra/tree/5.0-rc2-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1341/org/apache/cassandra/cassandra-all/5
The test build of Cassandra 5.0-rc2 is available.
sha1: 06691fce25a215361332aa1767e188bb6694687a
Git: https://github.com/apache/cassandra/tree/5.0-rc2-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1341/org/apache/cassandra/cassandra-all/5.0-rc2/
.
> 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
- so
reply below.
- since the project is Apache licensed we could fork / adopt for our needs?
> I’m not familiar enough with the hurdles we’d have to surmount around the
> licensing but at least it’s a compatible license. Maybe Mick knows more
> about what would be required for this route?
>
It's "C
reply below.
We're moving into a world where we will likely more frequently modify the
> mainline branch with new functionality to integrate with ecosystem changes
> (sidecar, analytics, drivers?). It's probably at least worth a conversation
> as to whether our current policy (improvements and ne
On Tue, 23 Jul 2024 at 15:27, J. D. Jordan
wrote:
> I don’t know that I agree we should remove use if isDebugEnabled, but we
> should be assuming debug is enabled and not doing anything too crazy there.
>
The problem is that the use of isDebugEnabled, as trivial as it is, leads
to the typical a
> I disagree with all of this. Debug logging *can* be enabled for
> production clusters, but it should not be on by default.
>
> DEBUG should *not* be taken to mean “background activities” and we should
> stamp this out wherever this has been occurring. DEBUG means verbose
> logging for use debuggi
reply below…
On Thu, 30 May 2024 at 14:34, Štefan Miklošovič
wrote:
> I see the feedback is overall positive. I will merge that and I will
> improve the documentation on the website along with what Benedict suggested.
>
I think the codestyle needs to be more explicit that this applies _only_
i, Jul 19, 2024 at 7:12 AM Joe Obernberger <
> joseph.obernber...@gmail.com> wrote:
>
>> Great news. Does anyone know if there have been updates to vectors
>> support and search?
>>
>> -Joe
>> On 7/18/2024 4:58 PM, Mick Semb Wever wrote:
>>
>&
The Cassandra team is pleased to announce the release of Apache Cassandra
version 5.0-rc1.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source
The Cassandra team is pleased to announce the release of Apache Cassandra
version 5.0-rc1.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source
> 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.
>
The vote passes with three binding +1s
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 correct
- source artefact
On Wed, 17 Jul 2024 at 21:40, Brandon Williams wrote:
> On Wed, Jul 17, 2024 at 2:36 PM Mick Semb Wever wrote:
> >
> > Should we remove the noboolean rpm from the release, given we have no
> way to verify or test it ?
> > Effectively, dropping centos:7 support from 5.0
On Mon, 15 Jul 2024 at 13:10, Brandon Williams wrote:
> +1
>
> Note that centos7 went EOL on June 30th; I didn't test the noboolean
> packages as a result.
>
Should we remove the noboolean rpm from the release, given we have no way
to verify or test it ?
Effectively, dropping centos:7 support
Proposing the third test build of Cassandra 5.0-rc1 for release.
sha1: d85d6750f90eaf799709a05d2f1c31189fce04fd
Git: https://github.com/apache/cassandra/tree/5.0-rc1-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1338/org/apache/cassandra/cassandra
.
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.
>
>
With a veto in place the vote fails.
Proposing the test build of Cassandra 5.0-rc1 for release.
sha1: 01eea8a0d74deaede236edb25335fa470502106e
Git: https://github.com/apache/cassandra/tree/5.0-rc1-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1337/org/apache/cassandra/cassandra-all/5
> The vote will be open for 72 hours (or longer). Votes by PMC members are
>> considered binding. A vote passes if there are at least three binding
>> +1s and no -1's.
>>
>
> Vote passes with 12 +1s (9 from PMC).
>
vote thread was
https://lists.apache.org/thread/j1tz0t90q72l3hp8frv9xzr0ozqstgg9
> The vote will be open for 72 hours (or longer). Votes by PMC members are
>> considered binding. A vote passes if there are at least three binding
>> +1s and no -1's.
>>
>
> Vote passes with 12 +1s (9 from PMC).
>
vote thread was
https://lists.apache.org/thread/j1tz0t90q72l3hp8frv9xzr0ozqstgg9
.
> The vote will be open for 72 hours (or longer). Votes by PMC members are
> considered binding. A vote passes if there are at least three binding +1s
> and no -1's.
>
Vote passes with 12 +1s (9 from PMC).
.
> The vote will be open for 72 hours (or longer). Votes by PMC members are
> considered binding. A vote passes if there are at least three binding +1s
> and no -1's.
>
Vote passes with 12 +1s (9 from PMC).
The votes fails with a veto in place having made CASSANDRA-19668 an 5.0-rc
blocker.
Once 19668 lands we will need an immediate release of 4.1.6 too.
On Fri, 28 Jun 2024 at 06:49, Jon Haddad wrote:
> Thanks for confirming this, Blake. I agree that we should not knowingly
> ship new versions wi
.
> The vote will be open for 72 hours (or longer). Votes by PMC members are
> considered binding. A vote passes if there are at least three binding +1s
> and no -1's.
>
+1
Please vote on the acceptance of the GoCQL driver and its IP Clearance:
https://incubator.apache.org/ip-clearance/cassandra-gocql-driver.html
All consent from original authors of the donation, and tracking of
collected CLAs, is found in:
- https://github.com/gocql/gocql/issues/1751
-
https://cwi
Please vote on the acceptance of the GoCQL driver and its IP Clearance:
https://incubator.apache.org/ip-clearance/cassandra-gocql-driver.html
All consent from original authors of the donation, and tracking of
collected CLAs, is found in:
- https://github.com/gocql/gocql/issues/1751
-
https://cwi
1 - 100 of 1066 matches
Mail list logo
