Fix EZP-24311: Clarify the differences between ezpublish-community and ezplatform repositories in README.md documentation - #12
Conversation
077cbd8 to
c35c2b3
Compare
|
Hello @sdaoudi Thank you for your prompt response and feedback. We have addressed the issues you brought up and rebased. We have also done the same in the corresponding ezpublish-community PR, ezsystems/ezpublish-community#239 Cheers, |
|
Thanks @brookinsconsulting 👍 |
c35c2b3 to
42f505e
Compare
|
review ping @bdunogier |
There was a problem hiding this comment.
"The eZ Publish 5 repository, mostly maintained for backwards compatibility, integrates eZ Publish Legacy..."
|
Let me know what you think of my suggestions. One last round, and we can merge this, as far as i am concerned. |
…d ezplatform repositories in README.md documentation
42f505e to
9c0f95c
Compare
|
Hello @bdunogier We have completed the changes requested and flattened. Cheers, |
|
+1 |
|
ping @bdunogier I noticed you closed the issue ticket, but you should also merge the ezplatform PR for the same issue ticket, #12 Cheers, |
…nces_doc Fix EZP-24311: Clarify the differences between ezpublish-community and ezplatform repositories in README.md documentation
|
Thank you :) Cheers, |
EZP-25522: User is not able to get variation of his profile image
4 participants
Hello,
Related issue for these pull requests: https://jira.ez.no/browse/EZP-24311
Per request from Andre to update the repository README.md documentation to clarify the differences between the older ezpublish-community repository and the new ezplatform repository in order to re-start community builds for the 5.x branch we are creating this issue.
Goal: Clarify the differences between the older ezpublish-community repository and the new ezplatform repository in repository README.md documentation.
To achieve this goal we will update the README.md documentation in each repository via separate pull requests to explain the main difference (today) between each repository is the inclusion or exclusion of legacy dependencies by default.
This pull request addresses the issue in question for this repository.
Another pull request exists for the other repository.
See issue ticket for alternate pull request links.
Please let us know how this finds you.
Thank you again for your continued support.
Cheers,
Brookins Consulting