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 tables containing what was deprecated and when. We have removed > all deprecated code from 1.x and 2.x in CASSANDRA-18959. > > > > We have put "since" into all Deprecated annotations in (2) just to track > when exactly it was deprecated. (I think we did a great job there as we > have way easier job right now when we contemplate about what to do with it). > > > > > We still have deprecated code from times of 3.x. If we go to release 6.0, > by the rules mentioned here, does it mean that all code which was > deprecated in 4.0 can be actually removed in 6.0? Hence, we can remove it > all basically right now? (As trunk will be 6.0, right?) > Just to clarify my proposal at least, I was talking about minimum windows after deprecation, not maximums. I like Benedict's simple "we don't break users" policy, but I got a bit confused when folks started talking about removing things after a mere *single* major release - which seems strange to me for anything that isn't a very minor breakage which breaks in a safe way as I mentioned.
