> ACCORD in particular was hyped in numerous talks and presentations and noone
> cautioned it might not hit 5.0, quite the opposite --so we need to ask
> ourselves how people who go on stage as Cassandra experts are not aware that
> it could slip.
I re-watched the New Orleans talks on Accord an
>
> The CEP process + dedicated development channels on ASF slack + public
> JIRA's + feature branches in the ASF repo we've seen with specifically TCM
> and Accord are the most transparent this kind of development has *ever
> been* on this project, and I'd argue right at the sweet spot or past
> w
nit: accord had no dependency on java17, it just wanted to drop support for java8 to make development easier due to bugs in the compiler. For some reason this got bundled into the work to support java17, but this was a false dependencyRegarding visibility, there’s a limit to how much time can be sp
I could not agree more with what Benjamin just wrote.
It is truly more about the visibility of the progress. If one looks at this
(1), well, that seems like a pretty much finished epic, isn't it? If we make ML
and Jira the only official sources of the truth, then there is no mentioning
whatoeve
> I also do not understand what has some session about TCM and Accord in "New
> Orleans" to do with it.
Stefan, please make sure to read the context, and re-read my message, since it
seems like you have completely misinterpreted it. My message states clearly
that I was responding to someone say
OK fair enough, I am taking that part back.
From: Alex Petrov
Sent: Monday, October 30, 2023 11:45
To: dev
Cc: Miklosovic, Stefan
Subject: Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate
5.1-alpha1)
NetApp Security WARNING: This is
(Note: You are receiving this because you are subscribed to the dev@
list for one or more projects of the Apache Software Foundation.)
It's back *and* it's new!
We're excited to announce that the first edition of Community over
Code Europe (formerly known as ApacheCon EU) which will be held at th
Hi everyone,
Please join us this Wednesday, November 1 for the monthly Cassandra Working
Group (CMWG) meeting at 8am PT / 11 ET / 3pm UTC.
Add your updates or new discussions/questions to the doc:
https://docs.google.com/document/d/1_73-iSjo1ZKKFn410rOCqNctnhNJOFLvbVA225OdrXY/edit
If you need a
He's talking about my Accord talks ;) I'm sure I've said quite a few times
that Accord is shipping with 5.0 at the end of 2023. That was a reasonable
thing to say, but new information, new updates.
If you scroll back 30-40 replies, I live-blogged my realization that's not
going to happen and comin
Hi,
similarly as for Cassandra 1.x and 2.x deprecations removal done in
CASSANDRA-18959, you are welcome to comment on the removal of all stuff
deprecated in 3.x (1).
If nobody objects after couple days I would like to proceed to the actual
removal. Please tell me if you want something to keep
Proposing the test build of Cassandra 5.0-alpha2 for release.
DISCLAIMER, this alpha release does not contain the features:
Transactional Cluster Metadata (CEP-21) and Accord Transactions
(CEP-15). These features are under discussion to be pushed to a
5.1-alpha1 release, with an eta still this ye
> similarly as for Cassandra 1.x and 2.x deprecations removal done in
> CASSANDRA-18959, you are welcome to comment on the removal of all stuff
> deprecated in 3.x (1).
>
> If nobody objects after couple days I would like to proceed to the actual
> removal. Please tell me if you want something t
Sure we can do that just for trunk. No problem with that. Hence, I am parking
this effort for a while.
From: Mick Semb Wever
Sent: Monday, October 30, 2023 22:56
To: dev@cassandra.apache.org
Subject: Re: Removal of deprecations added in Cassandra 3.x
Net
Hoping we can get clarity on this.
The proposal was, once TCM and Accord merges to trunk, then immediately
branch cassandra-5.1 and cut an immediate 5.1-alpha1 release.
This was to focus on stabilising TCM and Accord as soon as it lands, hence
the immediate branching.
And the alpha release as t
That is my understanding as well. If the TCM and Accord based on TCM branches are ready to commit by ~12/1 we can cut a 5.1 branch and then a 5.1-alpha release.Where “ready to commit” means our usual things of two committer +1 and green CI etc.If we are not ready to commit then I propose that as lo
15 matches
Mail list logo
