- Issue created by @volanar
- 🇺🇸United States thejimbirch Cape Cod, Massachusetts
There is no compatibility with Drupal CMS. The compatibility is with Drupal core.
Ask the maintainer of the module to create a release that supports Drupal 11 and it will be installable on Drupal CMS in project browser.
Drupal cms uses a lot of third-party modules, which is great. That's why I'm referring to the drupal cms, not the drupal core, since an important component of the drupal cms is the trouble-free operation of the core and third-party modules. Therefore, it's worth thinking about how to keep up-to-date third-party modules. You should not leave users alone with abandoned or rarely updated modules. Some modules have not been updated for years, but are used on thousands of sites. Users do not upgrade to new versions of drupal due to the fact that developers have abandoned or for some reason do not update modules. A strategy is needed to solve this problem. Because this is a global issue and no less important than the drupal core updates.
- 🇬🇧United Kingdom catch
@volanar see 🌱 [policy] Impact on contributed projects and its maintainers Active .
I think the specific point you're raising is partly because Drupal CMS was released not very long after Drupal 11.0.0 - so while there are over 3,000 projects with stable Drupal 11-compatible releases, there are 6,000 without.
However, it will be even more pronounced on the day 12.0.0 is released when you would still want new Drupal CMS sites to start on 12.0.0, and hence any dependencies to also have stable Drupal 12 compatible releases, but I think that's better discussed in the issue above.
Yes, you're right. There is no guarantee that a third-party module will not be broken with each update. Thanks for the link
Yes, you're right. There is no guarantee that a third-party module will not be broken with each update. Thanks for the link
Yes, you're right. There is no guarantee that a third-party module will not be broken with each update. Thanks for the link