> With the publication of this release I would like to switch the default 'latest' docs on the website from 4.1 to 5.0. Are there any objections to this ?
It looks like the switch of latest to 5.0 broken some top search links (returns 404 to me): [1] - https://www.google.com/search?q=apache+cassandra+configuration [2] - https://www.google.com/search?q=apache+cassandra+getting+started [2] https://www.google.com/search?q=apache+cassandra+install [3] - https://www.google.com/search?q=apache+cassandra+jdk Can/should we rollback while we add redirects to the old indexed links? On Sat, Nov 4, 2023 at 2:04 PM Ekaterina Dimitrova <e.dimitr...@gmail.com> wrote: > > 1. “No objections from me since these issues are mostly cosmetic, but > it would be nice to clear these before the next alpha/beta. I will create a > ticket for the unknown module warning later if nobody beats me to it.” > > > > 1. > > > 1. CASSANDRA-19001 > <https://issues.apache.org/jira/browse/CASSANDRA-19001> opened for the > issue to be checked. Until we have tested/investigated whether the features > that are supposed to use those modules experience any issues, this is an > isolated problem that might turn out to be a cosmetic one. So far, we know > the associated features and the JDK where the warnings are seen. > > > You are right, Paulo, I meant CASSANDRA-18711 is the one that will take > care of the Security Manager deprecation in the future. I just moved it out > of triage. > > Best regards, > Ekaterina > > > On Sat, 4 Nov 2023 at 7:15, Mick Semb Wever <m...@apache.org> wrote: > >> > As this is alpha release - can we open a ticket to be resolved in the >>> next alpha/beta? It is up to PMC to decide, of course. >>> >>> No objections from me since these issues are mostly cosmetic, but it >>> would be nice to clear these before the next alpha/beta. I will create a >>> ticket for the unknown module warning later if nobody beats me to it. >>> >> >> >> I agree. When these tickets are created please add fixVersion '5.0-beta' >> to indicate such. >> >> >>
