In CASSANDRA-17166 I am adding a test that detects breaking changes; this is
not compile time, rather test case time…
We sadly don’t document when a config is free to remove, we should do that to
enhance our warnings to users as well as make clear when free to remove; we
spoke about this in 4.0
“ We sadly don’t document when a config is free to remove, we should do
that to enhance our warnings to users as well as make clear when free to
remove; we spoke about this in 4.0 timeline that your deprecate in X.0.0
and remove in (X+1).0.0, we should document this in code for each config”
This a
Agree
Sent from my iPhone
> On Feb 13, 2022, at 5:53 AM, Ekaterina Dimitrova
> wrote:
>
>
> “ We sadly don’t document when a config is free to remove, we should do that
> to enhance our warnings to users as well as make clear when free to remove;
> we spoke about this in 4.0 timeline that
Proposing the test build of Cassandra 4.0.3 for release.
sha1: a87055d56a33a9b17606f14535f48eb461965b82
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.3-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1259/org