Re: [DISCUSS] How we version our releases

I can definitely see a logic in not removing. When I saw deprecated annotations for the first time after I mapped where we deprecated it, my initial desire was to invent some logic to remove it all after some period of time but that is not a good idea after all. We had a thread about this here (1)

Re: [VOTE] Simplifying our release versioning process

> > We have already agreed some time ago that any incompatible API change > requires a DISCUSS thread. I’m fairly sure it’s documented on the wiki. Yes, I remembered that we already have a thread to reach consensus on this. +1 on this vote. Mick Semb Wever 于2025年4月22日周二 13:35写道： > > . > >

Re: [VOTE] Simplifying our release versioning process

. > I'll plan to leave the vote open until we hit enough participation to pass > or fail it up to probably a couple weeks. > +1

Re: [DISCUSS] How we version our releases

On Mon, Apr 21, 2025 at 3:12 PM Miklosovic, Stefan via dev < dev@cassandra.apache.org> wrote: > Seeing this thread where we discuss about deprecations, I use this for > asking if there is some action to take when looking into (1) I conducted a > small research for some time ago. > > > > There are

Re: [DISCUSS] How we version our releases

On Mon, Apr 21, 2025 at 9:20 AM Josh McKenzie wrote: > Honestly, excepting thrift support I can't remember something we removed > from the system in this way so a lot of this is perhaps premature process > optimization. > That is definitely fair, as long as we don't go deprecating things after a

Re: [DISCUSS] How we version our releases

Seeing this thread where we discuss about deprecations, I use this for asking if there is some action to take when looking into (1) I conducted a small research for some time ago. There are tables containing what was deprecated and when. We have removed all deprecated code from 1.x and 2.x i

Re: [Committer/reviewer needed] Request for Review of Cassandra PRs

One more ticket has been reviewed by one committer and needs another committer to review. - Local Hints are stepping on local mutations [CASSANDRA-19958 ] Jaydeep On Mon, Apr 21, 2025 at 9:39 AM Runtian Liu wrote: > Hi, > A gentle

Re: [Committer/reviewer needed] Request for Review of Cassandra PRs

Hi, A gentle reminder on the following two changes: 1. *Inbound stream throttler* [CASSANDRA− 11303 ] 2. *Clear existing data when reset_bootstrap_progress is true* [ CASSAN

Re: [DISCUSS] How we version our releases

Honestly, excepting thrift support I can't remember something we removed from the system in this way so a lot of this is perhaps premature process optimization. And I agree w/you here Benedict; given we can shim in translation from new functionality to continue to support previous APIs (thinkin