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.

Sign up for GitHub

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

Simplify upgrading example: do not go from 2.5 to 6. #1826

Merged
merged 1 commit into from
Dec 20, 2024
Merged

Simplify upgrading example: do not go from 2.5 to 6. #1826

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions docs/backend/upgrading/intro.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,12 +114,10 @@ During in-place migrations, it is advisable **not to skip over** breaking (major

Going from Plone 5.2 to Plone 6.0 is fine.

If you are at Plone 2.5 and want to upgrade to the latest Plone 6, you should approach this in several steps:
If you are at Plone 4 and want to upgrade to the latest Plone 6, you should approach this in several steps:

- First upgrade from Plone 2.5 to the latest Plone 3 version (3.3.6).
- Then upgrade from Plone 3 to the latest Plone 4 version (4.3.20).
- Then upgrade from Plone 4 to the latest Plone 5 version (5.2.15).
- Then upgrade from Plone 5 to the latest Plone 6 version ({PLONE_BACKEND_PATCH_VERSION}).
- First upgrade from Plone 4 to the latest Plone 5 version.
- Then upgrade from Plone 5 to the latest Plone 6 version.


(introduction-upgrade-strategies-export-import-migrations-label)=
Expand Down
Loading