-
Notifications
You must be signed in to change notification settings - Fork 204
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
EZP-31735: As a Developer I'd like direct upgrade path from 1.13LTS to 2.5LTS #3048
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, if I understood your intention right, I would expect rather to-7.5.x.sql
or to-7.5.latest.sql
. It would be clear that this contains all the needed changes. Or is developer still expected to run all *-to-7.5.*.sql
scripts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One remark regarding the MySQL script itself:
This comment has been minimized.
This comment has been minimized.
Co-authored-by: Andrew Longosz <[email protected]>
Updated to go from 6.13.0 to 7.5.0 as the others. /cc @vidarl |
Co-authored-by: Gunnstein Lye <[email protected]>
@alongosz Better now? (It's now |
One thing though. |
@vidarl indeed it needs to be covered in doc as well so made note of it here: ibexa/documentation-developer#612 For the inline info in PR here it's ok or?
|
Yeah, it's ok. ( I missed it when reviewing yesterday, but I see it's there now ) |
As a Developer I'd like direct upgrade paths from LTS to LTS
7.5
TODO:
$ composer fix-cs
).