-
Notifications
You must be signed in to change notification settings - Fork 2k
Description
I find the deprecation policy to be contradictory (see https://jetty.org/docs/jetty/12.1/programming-guide/index.html#code-deprecation-policy).
Specifically whether we can remove deprecated code in micro releases (<major>.<minor>.<micro>).
As much as possible, deprecated code is not removed in micro releases. Deprecated code may be removed in major releases. Deprecated code may be removed in minor releases, but only if it has been deprecated for at least 6 micro releases.
This implies that we should not remove deprecated code in a micro release, unless absolutely necessary. They can be removed only at the start of a minor release if there has also been 6 micro releases.
The last paragraph seems to contradict this saying we can remove code in the micro releases.
On the other hand, code that was deprecated in Jetty 12.0.8 may be removed in Jetty 12.1.3 (because it has been deprecated for 3 micro releases in Jetty 12.0.x, and for 3 micro releases in Jetty 12.1.x — 12.1.0, 12.1.1 and 12.1.2).
I think we should come to a consensus whether we can remove code in micro releases, or only minor/major releases, and then clarify the wording of the deprecation policy.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status