> Personally, I think the removal of the deprecated code which was marked like
> that in 3.x is quite safe to do in 5.x but I have to ask broader audience to
> have a consensus.
Safe for us, sure. Safe for our users, not so much. No amount of including it
in release notes guarantees they'll see
>
> Personally, I think the removal of the deprecated code which was marked
> like that in 3.x is quite safe to do in 5.x but I have to ask broader
> audience to have a consensus.
Strawman:
Evaluate the cost and risk to us by having to keep the code.
Weigh that against the effort it takes for us
//github.com/apache/cassandra/pull/2853/files#diff-4e5b9f6d0d76ab9ace1bd805efe5788bb5d23c84c25ccf75b9896f20b46a1879
Thanks and regards
From: Miklosovic, Stefan via dev
Sent: Monday, October 30, 2023 23:07
To: dev@cassandra.apache.org
Cc: Miklosovic, Stefan
Subject: Re: Removal of deprecations added in
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
> 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
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
