Problem/Motivation

Track the steps needed to remove extension Tour from core to contrib. See Remove a core module and move it to a contributed project of the deprecation policy.

The removal of extension Tour was approved in #3325445: [Policy] Remove tour module from core.

Remaining tasks

  1. Create a child issue, 'Remove Tour from core'.
    • The change record for this issue should include a link to recommendations page, https://www.drupal.org/node/3223395#s-Tour. (For example, the CR for removing HAL)
    • Tag this issue 'Needs release note.'
    • Remove the extension ;-).
    • Remove references from core/phpstan-baseline.neon.
    • Remove any spelling words specific to the extension from the dictionary
    • Check for references in @todo.
    • Handle migration tests.
      • In all the functional tests in migrate_drupal_ui make sure that Tour is not installed. Tour should also be removed from the methods getAvailablePaths() and moved to getMissingPaths() in the tests using those methods.
  2. Deprecate the extension in the current minor development branch. If the next major branch is open, the extension can be removed via a separate patch (to avoid dependent patches), otherwise an issue should be opened to remove the extension once the next major branch is open. #3336033: [Meta] Tasks to deprecate Tour module
  3. Open an issue, 'Ensure that Tour does not get special core treatment' in the packages.drupal.org issue queue to ensure that the composer namespace for the contributed project matches the core one after removal. This is to allocate the drupal/Tour Composer namespace to contrib extension rather than the core extension.
  4. Manually test upgrading from the core extension to the contrib extension.
  5. Triage core issues for Tour in the core queue and move either to the contrib project or the relevant core component. Restore the status to what it was before it was postponed.
  6. Move all core documentation for Tour to the contrib project.
  7. When the issue in https://www.drupal.org/project/project_composer is Fixed update the documentation with the new Composer command.

Release notes snippet

Comments

quietone created an issue. See original summary.

quietone’s picture

Component: statistics.module » tour.module
catch’s picture

Priority: Normal » Major
Status: Postponed » Active

Due to us being on an outdated version of shepherd.js, bumping this to major. Also un-postponing now the policy issue is decided.

quietone’s picture