On 05.12.2019 13:41, Angela Schreiber wrote:
Hi Julian
Maybe you could elaborate a bit more about the reasoning of backporting the
deprecated API signatures using Guava 1.10? The reason for the deprecation was
the fact that we want to make breaking changes, right? And this is the kind of
change I would feel quite uncomfortable with when it comes to back port... when
it's just about the deprecation, I am not sure I understand the bigger benefit
of the back port... or do I misunderstand the overall goal behind this?
...
What I intend to backport are the changes that (a) deprecate the
existing API (that uses Guava) *and* (b) introduce replacements. Part
(b) is the one that will actually change the API (but in a
backward-compatible manner -> minor version change).
The reason for backporting to 1.10 is that this is the newest
maintenance branch we have. If we actually remove the Guava-based API in
a future trunk release (say 1.26.0), people migrating from 1.10.* to
that version would be very surprised (and have no supported version to
move to first which contains the replacement APIs).
Hopefully this clarifies things...
Best regards, Julian
