Looking at the board it is unclear to me why CASSANDRA-19011 <https://issues.apache.org/jira/browse/CASSANDRA-19011>, CASSANDRA-19018 <https://issues.apache.org/jira/browse/CASSANDRA-19018>, CASSANDRA-18796 <https://issues.apache.org/jira/browse/CASSANDRA-18796> and CASSANDRA-18940 <https://issues.apache.org/jira/browse/CASSANDRA-18940> are not beta tickets. SAI being one of the important features of 5.0 it seems to me that those tickets should have been handled for the beta release. CASSANDRA-19039 <https://issues.apache.org/jira/browse/CASSANDRA-19039> could also be a real problem.
Le dim. 26 nov. 2023 à 13:35, Mick Semb Wever <m...@apache.org> a écrit : > > Proposing the test build of Cassandra 5.0-beta1 for release. > > sha1: e0c0c31c7f6db1e3ddb80cef842b820fc27fd0eb > Git: https://github.com/apache/cassandra/tree/5.0-beta1-tentative > Maven Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-1319/org/apache/cassandra/cassandra-all/5.0-beta1/ > > The Source and Build Artifacts, and the Debian and RPM packages and > repositories, are available here: > https://dist.apache.org/repos/dist/dev/cassandra/5.0-beta1/ > > The vote will be open for 72 hours (longer if needed). Everyone who has > tested the build is invited to vote. Votes by PMC members are considered > binding. A vote passes if there are at least three binding +1s and no -1's. > > Remaining tickets to get us to 5.0-rc1 can be found on this jira board: > https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=593&view=detail > > [1]: CHANGES.txt: > https://github.com/apache/cassandra/blob/5.0-beta1-tentative/CHANGES.txt > [2]: NEWS.txt: > https://github.com/apache/cassandra/blob/5.0-beta1-tentative/NEWS.txt >