Refactor #10635
Formalize deprecation warnings
Description
We use different ways for deprecation warnins ::ActiveSupport::Deprecation.warn, logger.warn etc. We should introduce one way that would allow us to say in which version the deprecation will be dropped. Also it should make it easier to find things to drop during release process. One note about API parameters, we also need to mark parameters or whole entry points as deprecated but they won't be removed (just not included in next API version). apipie-rails will introduce deprecated option for params shortly.
Related issues
Associated revisions
Fixes #10635 - Formalize deprecation warning
(cherry picked from commit 319d1ffbed54f2c9eb988d132ec1586fb4d7c428)
History
#1
Updated by Ohad Levy almost 8 years ago
- Assignee set to Alon Goldboim
#2
Updated by The Foreman Bot almost 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2444 added
- Pull request deleted (
)
#3
Updated by Dominic Cleal over 7 years ago
- Category set to Plugin integration
- Legacy Backlogs Release (now unused) set to 35
#4
Updated by Alon Goldboim over 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 319d1ffbed54f2c9eb988d132ec1586fb4d7c428.
#5
Updated by Dominic Cleal over 7 years ago
- Related to Refactor #10988: Remove 1.11 deprecations added
#6
Updated by Dominic Cleal over 7 years ago
- Related to Refactor #10989: Remove 1.12 deprecations added
#7
Updated by Dominic Cleal over 7 years ago
- Related to Bug #11018: Taxonomy API updates throw "Invalid version format" deprecation-related error added
#8
Updated by Dominic Cleal about 7 years ago
- Related to Refactor #13845: Remove 1.13 deprecations added
Fixes #10635 - Formalize deprecation warning