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

Moving to a new namespace and package name #428

Closed
alexander-schranz opened this issue Oct 6, 2024 · 3 comments · Fixed by #458
Closed

Moving to a new namespace and package name #428

alexander-schranz opened this issue Oct 6, 2024 · 3 comments · Fixed by #458
Labels
DX Improves the developer experience features New feature or request
Milestone

Comments

@alexander-schranz
Copy link
Member

The project did begin as a research project and so I quickly created a schranz-search and used the Schranz\Search\SEAL\ namespace. This will be changed for 1.0 release. Currently different namespaces are in discussions. An upgrade via RenameNamespaceRector or via Search and Replace in your codebase should be easy.

What these also means is that we will may also move the name of the composer package. This sadly will loose our packagist statistic, but better early as later.

FYI: @ker0x, @Toflar

@alexander-schranz alexander-schranz added features New feature or request DX Improves the developer experience labels Oct 6, 2024
@alexander-schranz alexander-schranz added this to the 1.0.0 milestone Oct 6, 2024
@alexander-schranz alexander-schranz pinned this issue Oct 6, 2024
@alexander-schranz
Copy link
Member Author

In #458 we moved the project to the new organisation.

@jdreesen
Copy link
Contributor

May I ask what CMS-IG stands for?

@alexander-schranz
Copy link
Member Author

@jdreesen added a description to the organisation here: https://github.com/PHP-CMSIG

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DX Improves the developer experience features New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants