Problem/Motivation

This issue is to coordinate and track the steps needed to deprecate Tracker. See Remove a core module and move it to a contributed project of the deprecation policy.

The removal of tracker was approved in #1261120: Deprecate Tracker module in D10 and move to contrib in D11

Proposed resolution

Remaining tasks

  1. Move integrations implemented by other modules to Tracker module
    1. #3263793: Move tracker help topics to tracker module
    2. Move tests to Tracker module
    3. Handle Tracker migrations, #3204511: Deprecate tracker migration
  2. Create the contrib project, Tracker, with a stable release. https://www.drupal.org/project/tracker
  3. Deprecate the core Tracker module, #3261679: Deprecate tracker module in Drupal 10.1.x

User interface changes

API changes

Data model changes

Release notes snippet

Comments

quietone created an issue. See original summary.

quietone’s picture

Title: [Meta] Remove tracker module from core » [Meta] Remove tracker module from core and move to contrib
quietone’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes
quietone’s picture

Title: [Meta] Remove tracker module from core and move to contrib » [Meta] Tasks to deprecate Tracker
Issue summary: View changes
Parent issue: #1261120: Deprecate Tracker module in D10 and move to contrib in D11 » #3118154: [meta] Deprecate dependencies, libraries, modules, and themes that will be removed from Drupal 10 core by 9.4.0-beta1
quietone’s picture

Issue summary: View changes

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

spokje’s picture

xjm’s picture

Issue tags: +Drupal 11

 

catch’s picture

Issue summary: View changes
catch’s picture

I think #3204511: Deprecate tracker migration is not a blocker here since that migration (although it's completely wrong) is self-contained in the tracker module so would move with it to contrib. Tracker is already marked deprecated and has a stable contrib release, so can this be marked fixed?

quietone’s picture

Status: Active » Fixed

I completely agree with catch. There is more detail in the Issue summary of #3204511: Deprecate tracker migration.

Therefor, I am marking this fixed.

Status: Fixed » Closed (fixed)

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