We noticed in Katello that we will deprecate functionality and forget to actually remove the deprecated functionality. Here is an issue with some pretty egregious examples. Deprecated functionality from 3.5 still exists in the application today (we are on 3.15).
This doesn’t reflect well on us nor inspires a lot of confidence from our users. I am taking a look at adding testing for deprecation warnings, I have a draft PR up here: https://github.com/Katello/katello/pull/8554
This PR refactors the warnings so that they can be iterated through and the versions checked against the Katello version. This means when the release manager bumps the release, the tests will fail if the current Katello version is greater or equal to the intended deprecation version.
My question is: Has Foreman and/or other plugins seen the same problem and if so, should we add this functionality to Foreman?
We could make this functionality available to plugins and add this in a non-breaking way. I have some ideas on implementation, but want to make sure its a wanted feature in Foreman + plugins before adding it in Foreman.
Let me know if you have any questions, looking forward to some feedback