Re: [DISCUSS] Limitting the 4.0 GA scope

Thanks for the feedback Aleksey. I switched the fix version for CASSANDRA-16619 back to 4.0. Le jeu. 22 avr. 2021 à 18:25, Aleksey Yeshchenko a écrit : > I believe we wouldn’t knowingly ship a release with [CASSANDRA-16619 < > https://issues.apache.org/jira/browse/CASSANDRA-16619 < > https://i

Re: [DISCUSS] Limitting the 4.0 GA scope

I believe we wouldn’t knowingly ship a release with [CASSANDRA-16619 > Loss of commit log data possible after sstable ingest] in it, so I’d say at least that one needs to be fixed, even

Re: [DISCUSS] Limitting the 4.0 GA scope

> > it would probably help to send the link with the tickets being moved away > from GA so people can take a look more easily? > Good point Paulo. The tickets I moved to 4.0.X are the following. CASSANDRA-16547 Prioritisation for sized-tier

Re: [DISCUSS] Limitting the 4.0 GA scope

+1, but it would probably help to send the link with the tickets being moved away from GA so people can take a look more easily? Em ter., 20 de abr. de 2021 às 13:24, Benjamin Lerer escreveu: > Hi everybody, > > I had a look at the 4.0 GA tickets remaining and it looks like several > tickets ar

[DISCUSS] Limitting the 4.0 GA scope

Hi everybody, I had a look at the 4.0 GA tickets remaining and it looks like several tickets are not 4.0 specific. They are simply bugs that have been discovered recently (they exist in older releases). Unless the problem has been introduced in 4.0 or is a critical issue, it should probably not b