Thank you for your work and the prompt update, Maxim!
We seem to have a lazy consensus here so I suggest we continue all
operational discussions on the tickets themselves (not only the mentioned
ones but also any other dependency management tickets that might be open).
My understanding is that
A few updates.
We've posted a message to the user-list asking the question about the
use of the metrics-reporter-config library to make sure we are on the
safe side with the removal:
https://lists.apache.org/thread/c4m3tc08zhd4d41zs05jcdkr3gjwlhno
The issue for the
Thank you all. We are going to continue with those tickets and related
problems then.
On Maxim's question:
"Do we need a separate issue for 'org.caffinitas.ohc:ohc-core-j8' or we
should handle everything under [2]?"
It depends on whether someone has the time to sit and deal with the
complete
> I also want to hear if Abe still has concerns about not following deprecation
> process here.
I support removing the library on an expedited schedule, rather than waiting
for a full major of deprecation. We still have a large surface for metrics
integrations, and users who depended on
Hello everyone,
CASSANDRA-14667 when the 3.11.5 driver version with shaded metrics
dependencies is released, it will be fairly easy to handle the
cassandra-related part and get rid of the old metrics version in
Cassandra itself (the number of changes to the Cassandra part is also
minimal ~10
Given how early we are in the cycle with even the branch only recently cut (and how
much is not yet present in the alpha), housecleaning seems like a positive impulse.On
Aug 23, 2023, at 7:28 AM, Ekaterina Dimitrova wrote:Hi
everyone,I wanted to clarify something. I understood dependency
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
