[11.x] [Meta] Tasks to remove Statistics

There are both major only and minor targeted changes listed here. Not sure how to piece these apart, but moving to "Major versiono only" as per https://www.drupal.org/about/core/blog/new-drupal-core-branching-scheme-... → for now.

Since this is ContributionWeekend2024, I've created the separate repo from a git subtree split as described on https://www.drupal.org/about/core/policies/core-change-policies/module-o... →

As I'm not sure whether it's OK to create the drupal.org/project/statistics at this point, I've pushed the split to my github until that project is created https://github.com/fgm/statistics

Thanks @fgm, maybe just go ahead and register drupal.org/project/statistics, to make sure no-one else grabs it?

Someone already did and unpublished the module (or put it behind some access control) so I cannot do it. I prepared the project page with content explaining its status, so I can update that page if I get access to it at some point. Here is said content, pasteable to a Drupal project page,

I see ... I wonder if it was blocked a long time ago, to avoid confusing it with the core module? The Git repo doesn't exist: https://git.drupalcode.org/project/statistics

Maybe #1 ("File an issue in the project's queue [...]") and then straight to #6 ("If the owner does not reply after two weeks, move the issue to the Drupal.org project ownership issue queue [...]") is the process to pursue then?

https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... →

Discussion has been ongoing on Slack, @drumm should look into it soon.

The contrib Statistics project now has a build working for both 10.3.x and 11.x. Time to create a release ?

statistics 1.0.0-beta1 is released.

@andypost : could you clarify which work is needed, since you changed the status ? Is it just on the core side, or do I need to do something specific in the contrib version ?

@fgm, before this can be closed all the steps in the Issue Summary need to be completed. I think so far, only #2 is complete. Its a process with many parts.

Part (all ?) of 5. was done at DrupalCamp Roazhon: @vanessakovalsky and @hellosct1 reviewed the issues, closed a number of them, and commented the other ones, but did not move them because we had no explicit authorization from core maintainers to move the relevant issues to the contrib versions before the deprecation. Is it OK to move the issues now ?

I have been wondering how to perform 4, as I just do not see how that process can work. Any pointers ?

@fgm I bet the leftover is to move docs to contrib module, that's where I'm a bit stuck points 4 and 6 in summary)

@fgm, there are instructions → for testing the upgrade path. It doesn't look like that issue has been made for any of these removal yet.

I am going to update the template for the issue summary used for this type of issue to clarify that.

The Statistics module is in the Contributed module documentation on d.o. I removed the menu link from the Core module documentation.

I thought Step 3 was still to do but then found the issue. Adding as related.

To Do
Step 5. The are issues in the statistics.module component in core

Step 5: AFAICS there is no remaining open issue about statistics in core for 8.x, 9.x or 11.x. There is one issue which moved back from statistics to core 10.3 because it should be fixed in 10.3 which still contains the module, albeit deprecated.

Issues in 7.x have not been moved yet because D7 is still somehow supported until 01/2025. Do you think we should move them anyway, since they are unlikely to be addressed in core by that date ?

@fgm, thank you for confirming that! I think we can close this then.

Woohoo! Another one completed.

Thanks you to everyone who made this happen so smoothly!

Added the upgrade test issue 📌 Test the core to contrib upgrade path Active . After that we should be good.

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