I’m on vacation, so I’ll keep this brief. While its not the end of the world, I think shipping a feature that’s immediately deprecated reflects poorly on the project and our ability to manage it.
I don’t know how much work need to be done to merge that patch, so its hard to say if we should wait for it or if we should ship 5.0 and make an exception to add it in 5.0.1. I’d prefer 5.0.1 but i won’t die on this hill. Jon On Fri, Jun 21, 2024 at 11:35 AM Mick Semb Wever <m...@apache.org> wrote: > > > On Fri, 21 Jun 2024 at 09:43, Sam Tunnicliffe <s...@beobal.com> wrote: > >> 100% Option 1. Once it's out in GA release we're stuck with it so any >> short term disruption to adopters of pre-release versions is a trivial >> price to pay. > > > > Sam, Jeremiah, Jeff, Jon, > > we need some clarity on this. > > To remove MAXWRITETIME (CASSANDRA-18078) we must now (as Yifan notes) > first add CASSANDRA-18085. > > 18085 was slated for 5.x > Are we really going to both a) remove an API that was already released in > a beta, and b) add in a new improvement into an rc ? > > This is the only remaining issue blocking us from cutting a 5.0-rc1. > > >
