-
Incident report
-
Resolution: Unresolved
-
Trivial
-
None
-
None
API changes page currently contains two sections:
- Backward incompatible changes
- Other changes and bug fixes
For no better option, deprecated features are currently put under "Other changes and bug fixes". But this caption sounds neither important nor interesting, so there is very little intention to read them carefully.
There should be a dedicated section for deprecated features. This will emphasize to API consumers, what changes need to be done in advance to avoid necessity for immediate action after deprecated features are completely removed and appear in "Backward incompatible changes" section of a future release.
For example, Changes from 5.2 to 5.4 page does not even contain a word "deprecated", it just says:
user.login: Renamed parameter user → username.
Even though there was a transition period between deprecation and removal (ZBXNEXT-8085), the lack of proper communication did not allow Grafana plugin to adjust in time.