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

IBX-88: [Rebranding] Renamed ezpublish extension to ibexa #21

Merged
merged 4 commits into from
Nov 26, 2021

Conversation

alongosz
Copy link
Member

@alongosz alongosz commented Nov 24, 2021

Question Answer
JIRA issue IBX-88
Requires ibexa/compatibility-layer#3
Type feature
Target Ibexa version v4.0
BC breaks yes, requires ibexa/compatibility-layer#3

Core change:

With Ibexa Compatibility Layer Bundle it should be enough to run a fresh project installation, without 1st party changes.

There are also other changes getting rid of extension-related (directly and not directly) strings containing ezpublish. The ones prepending config and changing suggestions format are necessary, the others are cosmetic.

Aiming to merge it quickly to unblock further work, with possible follow-ups if something comes up by future QA tests.

Checklist:

  • Provided PR description.
  • Tested the solution manually.
  • Aligned automated test coverage.
  • Checked that target branch is set correctly
  • Ran PHP CS Fixer for new PHP code
  • Asked for a review (ping @ibexa/engineering).

@alongosz alongosz force-pushed the ibx-88-ibexa-extension-with-bc branch from 34bd2d2 to 25fe592 Compare November 26, 2021 11:18
@alongosz alongosz marked this pull request as ready for review November 26, 2021 11:18
@alongosz
Copy link
Member Author

CI failure appears on the main branch also, needs to be investigated separately. Merging. Aiming for QA at the end of the whole set of rebranding-related changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature request Ready for review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants