Hi Jan, On 4.11.2025 23:54, Jan Høydahl wrote: > SolrJ is part of our user-facing contract, and imo any breaking > change that will make the user's code no longer compile (such as package > change) needs a deprecation, and wait until next major to execute.
My two cents: Lately, I’ve seen quite a few users express frustration with deprecations (e.g. [1]). Many teams have strict policies that require addressing deprecated APIs immediately, and some even fail their builds when deprecations are present. Deprecating a class without providing an alternative will create unnecessary friction for these users. Piotr [1] https://lists.apache.org/thread/15trh8n443s4rnmtj95oh0vlbb8dr2h1 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
