Great idea! I don't know how well it will work in practice... I remember a
lot of the deprecation removals required a fair bit of disentangling in
3.0. It is probably not so bad for stuff we want to remove in 4.0, though.
On Wed, Mar 5, 2025 at 6:27 PM Dave Marion wrote:
> "Minor version Y (x.Y.
"Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backward
compatible functionality is introduced to the public API. It MUST be
incremented if any public API functionality is marked as deprecated..."
Ref: https://semver.org/#spec-item-7
If we wanted to maintain semver compliance, then
I was recently in a conversation where the question was raised about what
future versions of Accumulo are expected.
There was a time during the elasticity/4.0 development, before that was
merged into the main branch that I thought it would be a good idea to have
a 3.1 LTM release. However, most of
