[11.x] Remove tracker module from core

I think we need to fix the tests in separate issue ti unblock this one

the related may affect this tests

+++ b/core/modules/tracker/tracker.info.yml
@@ -6,3 +6,5 @@ dependencies:
+lifecycle_link: 'https://www.drupal.org/node/3261453'

I think the intention was that these would go to a handbook page with instructions for users, rather than a change notice

Should we split this into two issues - one for the deprecation in D9 (which can happen fairly fast) and one for the removal in D10 (which may take longer).

Don't want to postpone the deprecation if we can avoid it

Opened https://www.drupal.org/docs/core-modules-and-themes/deprecated-modules-a... for the lifecycle links

On #7, the fix here will conflict with #3261486: Remove core updates added prior to 9.3.0 and adjust test coverage.

The way to resolve it (I think), will be to load the fixture database dumps into whichever Drupal version they were created with (i.e. if it's after that issue lands, then 9.3.0), uninstall tracker, then dump the fixtures back again.

Agreed with @larowlan it would be good to split this into separate deprecation and removal issues so the deprecation can land in 9.4.x asap - that can happen as soon as there's a release of the contrib module.

#3204511: Deprecate tracker migration is an existing bug with the tracker migration, but I don't think needs to block this, could be resolved in the contrib module.

I just committed #3263793: Move tracker help topics to tracker module and backported to 9.4.x, opened an issue against the contrib module here: #3263793: Move tracker help topics to tracker module.

I think that means this is unpostponed, but tests still failing here.

Progress. The last failure is Drupal\Tests\system\Functional\UpdateSystem\UpdatePathTestBaseFilledTest

Wrong issue.

The whole Tracker module gets removed from core.
A number (migrate) get changed, because the Tracker module is not there anymore.
All changes look good to me.
For me it is RTBC.

Added release note snippet and updated CR.

Postponing on #3291265: \Drupal\Tests\forum\Functional\ForumNodeAccessTest doesn't use tracker module

Weirdly that test enables the tracker module (unneeded), so I would expect the TestBot run to show that test complaining about the tracker module not being there.

That didn't happen. _shrug_

Turns out (I must remember to read the meta-issue first before diving into these issues...) this is postponed on:

#3271124: Move all non migration Tracker tests to the module in preparation of removal
#3291265: \Drupal\Tests\forum\Functional\ForumNodeAccessTest doesn't use tracker module

Blocker #3291265: \Drupal\Tests\forum\Functional\ForumNodeAccessTest doesn't use tracker module landed.

Remaining blocker #3271124: Move all non migration Tracker tests to the module in preparation of removal landed.

Postponed on #3291599: Ensure that tracker does not get special core treatment per Slack discussion here: https://drupal.slack.com/archives/C014CT1CN1M/p1655750184381089
Also needs manual testing when that blocker lands (see also Slack discussion)

The main thing we need to do before removing them from 10.0.x is ensure that the composer façade naming for them is fixed, and have someone manually test EACH to confirm downloading the contrib module in D9 and installing it works SEAMLESSLY, and that it then does again if the rm -rf core/modules/foo

Removing tag until this is ready. Thanks!

I think this is at the point where it can land once the 11.0.x branch is actually open.

Changing the parent to the removal meta.

Updating title, tags and version number based on recent announcement at https://www.drupal.org/about/core/blog/new-drupal-core-branching-scheme-...

Thanks for cleaning up, and keeping Drupal lean. I found this issue while looking for a solution to a Tracker-related error during a Drupal 7 to Drupal 10 migration of Views:

Source ID tracker: VIEW: tracker DISPLAY: default - The 'uid_touch' argument Plugin is missing and will be listed as broken.
Source ID tracker: VIEW: tracker DISPLAY: default - The field timestamp does not exist and has been removed from the fields configuration.

The solution was to delete the Contextual filters "User posted or commented" field from the Tracker view (it could not be deleted).

old MR needs rebase, I opened new to check other aproach instead of clean-up of dumps

Got tests green with fixtures clean-up https://git.drupalcode.org/project/drupal/-/merge_requests/7358 (split into 3 commits)

Not possible to use obsolete stub here as there's configuration tracker.settings in the filled dump, so probably it should wait for fixtures update

The Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.

Ready to go

Overall looks good, but a couple of questions on the MR.

Took a look at the two comments but they appear to already be in getMissingPaths() seems correct based on d6 migration tests.

Rests looks good.

Ahh thanks for checking properly, just the @todo was wrong then.

Committed/pushed to 11.x, thanks!

Update version to the branch this applies to.