Problem/Motivation

This issue is to set the module status to deprecated.

The removal of extension History module was approved in #3336276: [Policy] Deprecate History module.

Remaining tasks

  1. Create a section on Deprecated and obsolete modules and themes to provide recommendations for sites using extension History. The recommendations are to include instructions for sites using the extension and for contributed projects that depend on then extension.
  2. Add the following to the extension info.yml file

    3. lifecycle: deprecated
    lifecycle_link: https://www.drupal.org/node/3223395#s-history

  3. Add @group legacy to all tests in the extension.
  4. Add a change record and include a link the the doc page.
  5. Deprecate any library that is only used by the extension.
  6. Do a thorough search of core for any remaining references to the extension. If references are found, outside of the extension, then creates issues to remove the references.

Release notes snippet

Issue fork drupal-3520472

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

quietone created an issue. See original summary.

quietone opened merge request !14349

quietone’s picture

quietone commented
Status: Postponed » Needs review
longwave’s picture

longwave
he/him
Primary language English
Location UK
commented
Status: Needs review » Reviewed & tested by the community

I think this is all that is needed here.

catch’s picture

catch
he/him
Primary language English
commented

Does https://www.drupal.org/project/history need to be sorted out first? Technically it shouldn't matter as long as it's ready before the 11.4.x beta but I think we've held the actual deprecation on the project being in place before.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.

longwave’s picture

longwave
he/him
Primary language English
Location UK
commented

@andypost has tagged https://www.drupal.org/project/history/releases/1.0.0

  • catch committed a2dba268 on main 
    task: #3520472 Deprecate the History module

By: quietone
catch’s picture

catch
he/him
Primary language English
commented
Version: main » 11.x-dev
Status: Reviewed & tested by the community » Fixed

Committed/pushed to main and 11.x, thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

catch closed merge request !14349

  • catch committed 0354143a on 11.x 
    task: #3520472 Deprecate the History module

By: quietone
(cherry picked...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

quietone’s picture

quietone commented
Issue tags: +11.4.0 release notes
sam711’s picture

sam711 commented

How is https://www.drupal.org/project/history a replacement for the core history module? I think these two modules are unrelated.

https://www.drupal.org/node/3223395#s-history

quietone’s picture

quietone commented

Do you have a specific concern?

The parent issue has comments from andypost, who agreed to maintain the contrib version. In comment 8 they provided a link to the contrib history module they created.

Also, the upgrade process is manually tested to ensure that the functionality of history still works. That was done in [#/3586200].

sam711’s picture

sam711 commented

The core module description is:
"Records which content users have viewed and marks it as new or updated."
While the contrib history module, linked on the help page states:
"Node History is a replacement for the revision list built into the node module."

To me, the core module is Analytics and the contrib module is Editorial. I do not see this as an immediate replacement that can be generally recommended.

quietone’s picture

quietone commented

The description on the project page is wrong then and needs an update. You can make an issue in the project about that.

This description in the info yml file for the project is correct,