We don't have a formal way to deprecate modules in core. In
#3062281: Deprecate block_place module for removal in Drupal 9 →
, we deprecated the Place Block module by deprecating basically everything inside it, including the .module file itself. The module had already been hidden in a previous minor release. It was a bit tedious and ad-hoc, and took a long time to implement even though we were deprecating a module that had been already hidden for many releases.
This issue is not for defining the conditions under which a module will be deprecated; that's a separate product management discussion. Rather, it's for discussing how to deprecate a module once the decision has been made to do so.
Use the lifecycle property in the info.yml of the module to deprecate and eventually remove the module from Drupal core. To deprecate a module change the lifecycle property to lifecycle: deprecated and add lifecycle_link: link to CR, In the next major release change the lifecycle property to lifecycle: obsolete and add lifecycle_link: link to CR. Also add an update to uninstall the module.
There are two possible scenarios:
What happens as a result will depend on which of these scenarios are the case.
TBD
TBD
TBD
TBD
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
All the child issues but one have been fixed. Typically, an meta issue can be closed when that happens but there is one remaining question.
Can rector or Project Update Bot do anything with this, e.g. replace a dependency on a deprecated extension with its replacement or contrib equivalent?