Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CODE TASK] Update all modules to drupal/ namespace in Composer #2270

Open
rosiel opened this issue Nov 9, 2023 · 1 comment
Open

[CODE TASK] Update all modules to drupal/ namespace in Composer #2270

rosiel opened this issue Nov 9, 2023 · 1 comment
Labels
Type: bug identifies a problem in the software with clear steps to reproduce

Comments

@rosiel
Copy link
Member

rosiel commented Nov 9, 2023

We have moved our modules to drupal.org, though they are still available through packagist. We ought to harmonize our modules to use one namespace (drupal/), and take care of this so it's a smooth transition.

Steps/suggestions:

  • Change composer.json's top-level name: key to use the drupal namespace.
  • Add a replace key that includes the old namespace, at all versions. This way things other packages that require islandora/islandora can be satisfied by drupal/islandora.
  • Update packagist to mark our packages as abandoned(?!!), and suggest the new namespace.

I want there to be little fuss and so I'm looking for feedback on what to do.

@rosiel
Copy link
Member Author

rosiel commented May 28, 2024

The above PRs do not close this issue. As decided in Islandora/islandora#1020, we're going to keep this open for 3 months to provide a buffer time after the deprecation notice. Then, we'll actually change the main namespaces in the composer.json files. That'll make everything easier to use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: bug identifies a problem in the software with clear steps to reproduce
Projects
None yet
Development

No branches or pull requests

1 participant