The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Tarballs
Deprecation infrastructure
JavaScript Dependencies
- #3076171: Provide a new library to replace jQuery UI autocomplete
- #2158943: PP-1 Add a native dialog element using HTMX to deprecate the jQuery UI dialog
- #3203920: Replace Contextual Links BackboneJS usage with VanillaJS equivalent
PHP dependencies
- Remove doctrine once #3396165: [meta] Convert all core plugin types to attribute discovery is complete
- Archive_Tar: #3556706: Deprecate ArchiverManager and ArchiverInterface
Libraries
Modules
- ✅Ban #3482198: [meta] Tasks to deprecate the Ban module
- ✅Contact #3520460: [meta] Tasks to deprecate the Contact module
- ✅Field Layout #3517712: [meta] Tasks to deprecate the Field Layout module
- ✅History #3520462: [meta] Tasks to deprecate the History module
- ✅Migrate Drupal #3315257: [meta] Tasks to deprecate Migrate Drupal
- ✅Migrate Drupal UI #3463321: Deprecate Migrate Drupal UI
- Search #3565780: [meta] Tasks to deprecate the Search module
- ✅Settings Tray #3576667: [meta] Tasks to deprecate Settings Tray
- ✅Shortcut #3569117: [meta] Tasks to deprecate the Shortcut module
- ✅Telephone #3594196: [meta] Tasks to deprecate the Telephone module
- Toolbar #3484850: [meta] Tasks to deprecate Toolbar module
Themes
- Claro #3576668: [meta] Tasks to deprecate Claro
- ✅ Stable 9 #3560200: [meta] Tasks to deprecate Stable 9
- Olivero #3595082: [meta] Tasks to deprecate the Olivero theme
Experimental Modules
Remaining tasks
- Add additional issues as appropriate.
- Evaluate in early 2023, again after 10.2.0-beta1, and again prior to 10.3.0-alpha1.
Comments
Comment #2
xjmAmending attribution.
Comment #3
catchComment #4
quietone commentedComment #5
quietone commentedComment #6
quietone commentedComment #7
quietone commentedComment #8
quietone commentedComment #9
quietone commentedComment #10
catchThe very latest we can deprecate these modules is in the same minor release that comes out when 12.0.0 is released, but there are multiple steps involved before actual deprecation so it's really time to get this moving now.
Comment #11
xjmI added a stub CTA about this in our post draft at the end:
Comment #12
quietone commentedAdd issue for ArchiveTar
Comment #13
quietone commentedComment #14
quietone commentedComment #15
quietone commentedComment #16
quietone commentedComment #18
quietone commentedComment #19
quietone commentedComment #20
quietone commentedWrong issue
Comment #21
andypostsearch and shortcut has policy issues RTBC but stable9 and toolbar are blocked and not clear who can take a maintainer badge
Comment #22
andypostComment #23
andypostComment #24
andypostComment #25
ressaThanks for maintaining Drupal and trimming the core modules when needed.
Maybe we could consider adding a sentence about becoming contrib maintainer in each deprecate Drupal core module Meta issue?
As an example, in #3484850: [meta] Tasks to deprecate Toolbar module it could be something like below (the "Want to become a contrib maintainer ..." part):
Comment #26
quietone commentedComment #27
eduardo morales albertiArchiverTar should also be removed and replaced by https://www.php.net/manual/en/class.phardata.php
Comment #28
quietone commentedComment #29
quietone commentedComment #30
quietone commentedComment #31
quietone commentedComment #32
quietone commentedComment #33
quietone commentedComment #34
quietone commentedComment #35
quietone commentedComment #36
quietone commentedComment #37
quietone commentedComment #38
quietone commentedComment #39
quietone commentedComment #40
catch#3549134: Move text_with_summary to its own module is RTBC which should make it possible to deprecate and move to contrib immediately afterwards. Because it wasn't a module yet it wasn't on this list, but we should probably open the bits that are relevant. As far as I know, all the test coverage prerequisites are already done in that issue and its predecessors.