EZP-31735: As a Developer I'd like direct upgrade path from 1.13LTS to 2.5LTS

[andrerom]

Question	Answer
JIRA issue	EZP-31735 As a Developer I'd like direct upgrade paths from LTS to LTS
Bug/Improvement	yes
Target version	7.5
BC breaks	no
Tests pass	N/A
Doc needed	yes (to reach goal of story)

TODO:

• Implement feature / fix a bug.
• Implement tests.
• Fix new code according to Coding Standards ($ composer fix-cs).
• Ask for Code Review.

[alongosz]

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?

[alongosz]

One remark regarding the MySQL script itself:

[andrerom]

Updated to go from 6.13.0 to 7.5.0 as the others. /cc @vidarl

[andrerom]

@alongosz Better now? (It's now dbupdate-6.13.0-to-7.5.0.sql to eliminate any indications it will be kept updated for minor versions)

[vidarl]

One thing though. dbupdate-6.13.0-to-7.5.0.sql doesn't mention anything in regards to dbupdate-7.1.0-to-7.2.0-dfs.sql. It should be mentioned in any doc page using dbupdate-6.13.0-to-7.5.0.sql that you'll also need to run dbupdate-7.1.0-to-7.2.0-dfs.sql if you're using cluster

[andrerom]

@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?

-- IMPORTANT:
-- * If you use DFS (cluster), also make sure to apply "dbupdate-7.1.0-to-7.2.0-dfs.sql"
-- * This only covers eZ Platform kernel, see doc for all steps (incl. database schema) needed when updating: https://doc.ezplatform.com/en/2.5/updating/updating_ez_platform/

[vidarl]

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 )