Hi everyone, I wanted to clarify something. I understood dependency updates/cleaning can also be done in an alpha release if they lead to minimal user-facing changes, if any at all. I agree with that in our first 5.0 alpha release because we are not yet feature-complete. It is a good time for people to do a bit of housekeeping and tighten some loose ends. Do you think this is a valid statement? Thoughts? I wanted to clear this topic as we have a few in-flight tickets/discussions:
1. - CASSANDRA-14667 <https://issues.apache.org/jira/browse/CASSANDRA-14667> - upgrade dropwizard metrics, for which to be accommodated, Bret is creating a new 3.11.4 drivers version. So we should update the driver. I am unsure how much effort and change it will be on our side to update the drivers though. Maxim, did you try it? Any thoughts? 2. 1. 1. - CASSANDRA-18789 <https://issues.apache.org/jira/browse/CASSANDRA-18789> - commons-lang3, a pretty non-controversial bump with two versions. The one we are on is tested to Java 11, and the newest one tests up to JDK17 and beyond. This is enough reason for me honestly to update it. 2. 1. 3. 2. - In [1], Maxim mentioned that we can clean org.caffinitas.ohc:ohc-core-j8. - In [2], Stefan and Mick made a point that we could even remove in 5.0 metrics-reporter-config(CASSANDRA-18743) and commons-codec(CASSANDRA-18772) I think this should be a good idea - let's make some noise in the user group to ensure people are aware and no one raises any significant concerns and then clean those two. I also want to hear if Abe still has concerns about not following deprecation process here. And if we decide, we can find a few more loose ends to deal with. I am sure. Looking forward to your feedback and thoughts. Best regards, Ekaterina 1. [1] https://lists.apache.org/thread/9m1vz5qyows97wlppkwk1fd8386rj9q1 [2] https://lists.apache.org/thread/9m1vz5qyows97wlppkwk1fd8386rj9q1
