On 07/03/2020 09:13, Michael Osipov wrote:
> Folks,
>
> just wanted to make sure to avoid reverts.
>
> I want to start to drop all deprecated stuff I have marked/participated
> in the last couple years. What if a public API contains a typo? Are we
> fine to rename that?
It depends on how public the public API is and how long it has been
present. We are sometimes a little more relaxed about what is
technically a public API but is deep inside the Tomcat internals and has
only recently been added.
We try and keep compatibility between major versions if we can.
Usually, API changes are fine in the current development branch up to
the point where it is declared stable. Then we need to be more careful.
At the moment, removal in 10 is probably OK provided the code is
deprecated in 9.0.x with a note it will be removed in 10.0.x.
Fixing typos would normally be done by adding the correct method and
deprecating the old one.
There aren't any hard and fast rules. Some of this is subjective rather
than objective.
Reverting stuff isn't a big deal but you can always provide a PR for
review if you want to get feedback first.
Oh, and we can't touch the spec APIs. We have to follow what the Jakarta
projects do.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
