On Thu, 20 Jun 2024 at 18:46, Štefan Miklošovič <smikloso...@apache.org> wrote:
> List, > > we need your opinions about CASSANDRA-18078. > > That ticket is about the removal of MAXWRITETIME function which was added > in CASSANDRA-17425 and firstly introduced in 5.0-alpha1. > > This function was identified to be redundant in favor of CASSANDRA-8877 > and CASSANDRA-18060. > > The idea of the removal was welcomed and the patch was prepared doing so > but it was never delivered and the question what to do with it, in > connection with 5.0.0, still remains. > > The options are: > > 1) since 18078 was never released in GA, there is still time to remove it. > 2) it is too late for the removal hence we would keep it in 5.0.0 and we > would deprecate it in 5.0.1 and remove it in trunk. > > It is worth to say that there is a precedent in 2), in CASSANDRA-17495, > where it was the very same scenario. A guardrail was introduced in alpha1. > We decided to release and deprecate in 5.0.1 and remove in trunk. The same > might be applied here, however we would like to have it confirmed if this > is indeed the case or we prefer to just go with 1) and be done with it. > Option (2) is my vote. Rationale: it's our agreed guidelines, we say it hasn't been released but that's not accurate as we consider betas releases in this context. It's also the correct approach to take that we shouldn't ever try to avoid. It should never be a big deal to deal with a deprecate cycle regardless of how likely we think it isn't needed. I think this is especially true when we are right at the cusp of cutting 5.0-rc1, and effectively been in rc mode for a while now. (Yifan's comment hits this point on – not ever rush something at the last minute.) But I also have no objections if a waiver to our release lifecycle is agreed upon. Let common sense prevail – I haven't personally dug into the issue.
