[meta] Tasks to deprecate the History module

Open on Drupal.org →

Created on 22 April 2025, 3 months ago

Problem/Motivation

Track the steps needed to deprecate extension History module. See Remove a core module and move it to a contributed project → of the deprecation policy.

The removal of extension History module was approved in 🌱 [Policy] Deprecate History module in D10 and move to contrib in D11 RTBC .

Remaining tasks

Begin finding someone to maintain the contrib version of the extension.
Move integrations implemented by other modules to the extension.
Create child issues or child meta issues, as needed, to address the following points. Not all points will apply to all extensions.
- Move non-migration tests to the extension.
- Move Help Topics to the extension.
- For a theme, move theme-specific integration to the theme.
- Remove the extension from one or more profiles.
- Remove references to the extension from database dumps.
- Remove templates from the extension’s markup.
  - Remove templates from themes that are staying in core, leave them in deprecated themes
  - Keep skipping the template in the stable copies test.
- For a module, handle migrations, if the module has migrations.
  1. Copy the drupal 6 and drupal 7 test fixtures to the module so they remain independent of any core changes to the fixture.
  2. Migration yml and processes that are in the module move with the module to contrib.
  3. Move migration tests to the module.
  4. Keep all the assertions in core tests related to module as much as possible.
  5. Migration yml and processes that are outside the module but support the upgrade path for that module stay in core.
  6. The functional tests in migrate_drupal_ui will need to change.
  7. The drupal 6 and drupal 7 test fixtures stay the same.
Do a thorough search of core for any remaining references to the extension. If references are found, outside of the extension, then create issues to remove the references.
Create the contrib project with a stable release, before the alpha version of the major release. Follow the process in Create the contrib project with a stable release → for creating the sub tree split.
Deprecate the core extension. Use the Issue Summary template or core extension deprecation → .

📌 Task

Status

Active

Version

11.0 🔥

Component

contact.module

Created by

🇳🇿New Zealand quietone

Live updates comments and jobs are added and updated live.

Sign in to follow issues

Comments & Activities

Issue created by @quietone
Comment 3 months ago →
🇳🇿New Zealand quietone
Comment 3 months ago →
🇫🇷France andypost
Filed contrib issue to start ball roll 💬 Add andypost as co-maintainer to transfer core history module Active
Comment 3 months ago →
🇳🇿New Zealand quietone
Comment 3 months ago →
🇳🇿New Zealand quietone
Comment 10 days ago →
🇨🇭Switzerland berdir Switzerland
Started commenting in 📌 Remove uage of history module from comment module Active but moving into this issue.

I wonder if the decision to remove history module took into consideration how many features in comment module depend on it, there's a reason that history remained in core until now, this is going to be tough to untangle. That said, it's also clear that not a lot of sites these days actually rely on this feature (based on personal experience). The same can be said about comment module too I suppose.

Removal of history in D12 seems to conflict with new deprecation policy a bit. We will need to deprecate controllers/routes, views handlers, libraries and functionality to be able to remove history. It will likely not affect many modules in practice, if at all, but still, it's quite a lot and it would need to land very soon.

Might need to move history removal to D13.

I actually wonder if we should consider to instead just move comment.module as well into contrib and keep them entangled?

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024