Problem/Motivation

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

The removal of Settings Tray was approved in #3576315: [policy, no patch] Move Settings Tray to a contributed project.

Remaining tasks

  1. ✅Create a child issue, 'Remove Settings Tray from core' #3586218: Remove the Settings Tray module
  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.
  3. ✅Manually test upgrading from the core extension to the contrib extension. #3586207: Test the upgrade path for the Settings Tray module
  4. ✅Triage core issues for Settings Tray 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. Also, is the issue moved to contrib, then move any change record.
  5. ✅ Move all core documentation for Settings Tray to the contrib project. Make issues in the contrib project to update or add links to the documentation on the project page.
  6. ✅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

Issue summary: View changes
Status: Active » Postponed
gábor hojtsy’s picture

Status: Postponed » Active

https://www.drupal.org/project/settings_tray is now available (but not yet propagated).

cosmicdreams’s picture

Fresh code is in https://www.drupal.org/project/settings_tray. Ready for reviews and next steps.

I had to fix some linting issues and a test to get the CI to be happy.

quietone’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes
quietone’s picture

The last task here is to triage and move issues to the contrib project. When I try I get the following error, "Issues are not enabled for this project. You will not be able to submit this form." It looks like issues are now on GitLab. I've asked in #gitlab-issues-feedback.

cosmicdreams’s picture

I've looked into this. And it looks like I at least have the ability to create issues for the project.

quietone’s picture

Documenting here, for now, what is done when moving issues for a removed extension from Core to the contrib project.

For each issue

  • Move any draft change record to the contrib project
  • Set the status back to what is was before the 'Postponed' message
  • Change the Project field to the correct contrib project
  • Decide what version to use, typically it is the latest dev
  • Save
  • Adjust 'following' for the issue

There are 26 issues to move. They are the ones with status of "Postponed" and "Postponed (maintainer needs more info)"

quietone’s picture

Issue summary: View changes
Status: Active » Fixed

The Settings Tray issues were moved to the contrib project about a week ago in https://git.drupalcode.org/project/drupalorg/-/work_items/3607011#note_2...

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.

Status: Fixed » Closed (fixed)

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