-
Task
-
Resolution: Unresolved
-
Minor
-
None
-
3.8
-
MOODLE_38_STABLE
Right now we only have these dev docs talking about the deprecation process:
- https://moodledev.io/general/development/policies/deprecation
- https://moodledev.io/general/projects/api/string-deprecation
This issue is about to complete missing information about other deprecations that have some differences with the general deprecation process. Mainly:
- classes deprecation (see
MDLSITE-6729). - events deprecation (we have already deprecated some, look for
MDL-18592orMDL-63211for example). - external functions deprecation (there is only a 1-line note in the current docs, pretty vague).
MDL-55580: capabilities deprecation (to be decided, but there are a number of cases awaiting for it, seeMDL-55580).- behat steps deprecation (it already exists, but, needed for plugins, see
MDL-73669). - adhoc tasks
- scheduled tasks
- JavaScript (MDLSITE-6080)
- CSS (
MDL-78334) - constants (i.e. not class constants)
- icons (
MDL-82212) - <<any other thing that we consider is not covered by any of the above, feel free>>
Ciao
- has a non-specific relationship to
-
MDLSITE-6039 Clarify deprecation and backport policies surrounding templates
- Open
-
MDL-73669 Allow to create multiple behat_*_deprecated files, one in each component or plugin
- Closed
-
MDL-79843 Introduce mechanism for plugin type deprecation
- Waiting for integration review
-
MDLSITE-4689 Policy about function parameters on final deprecation
- Open
-
MDLSITE-6080 Decide on a deprecation policy for JS
- Open
-
MDL-55580 Process for deprecating a capability
- Closed
-
MDLSITE-6729 Deprecation policy does not detail what to do with deprecated classes for final deprecation
- Closed
-
MDL-55171 Extend deprecation policy to remove old deprecations
- Open
-
MDL-78334 Provide a mechanism to deprecate and detect deprecated CSS
- Closed
-
MDL-82212 Provide a mechanism to deprecate and detect deprecated icons
- Closed
- will be (partly) resolved by
-
MDL-80274 Amend the final deprecation process
- Open