Release notes & upgrade information

Some versions of django CMS present more complex upgrade paths than others, and some require you to take action. It is strongly recommended to read the release notes carefully when upgrading.

It goes without saying that you should backup your database before embarking on any process that makes changes to your database.

• 5.1.0 release notes
• 5.0.0 release notes
• 4.1.6 release notes
• 4.1.5 release notes
• 4.1.4 release notes
• 4.1.3 release notes
• 4.1.2 release notes
• 4.1.1 release notes
• 4.1.0 release notes
• 4.0.0 release notes
• release notes 3.11.5
• release notes 3.11.4
• release notes 3.11.3
• release notes 3.11.2
• 3.11.1 release notes
• 3.11.0 release notes
• 3.10.1 release notes
• 3.10.0 release notes
• 3.9.0 release notes
• 3.8.0 release notes
• 3.7.4 release notes
• 3.7.3 release notes
• 3.7.2 release notes
• 3.7.1 release notes
• 3.7.0 release notes
• 3.6.1 release notes
• 3.6.0 release notes
• 3.5.4 release notes
• 3.5.3 release notes
• 3.5.2 release notes
• 3.5.1 release notes
• 3.5.0 release notes
• 3.4.7 release notes
• 3.4.6 release notes
• 3.4.5 release notes
• 3.4.4 release notes
• 3.4.3 release notes
• 3.4.2 release notes
• 3.4.1 release notes
• 3.4 release notes
• 3.3 release notes
• 3.2.5 release notes
• 3.2.4 release notes
• 3.2.3 release notes
• 3.2.2 release notes
• 3.2.1 release notes
• 3.2 release notes
• 3.1.5 release notes
• 3.1.4 release notes
• 3.1.3 release notes
• 3.1.2 release notes
• 3.1.1 release notes
• 3.1 release notes
• 3.0.16 release notes
• 3.0.15 release notes
• 3.0.14 release notes
• 3.0.13 release notes
• 3.0.12 release notes
• 3.0.11 release notes
• 3.0.10 release notes
• 3.0.9 release notes
• 3.0.8 release notes
• 3.0.7 release notes
• 3.0.6 release notes
• 3.0.3 release notes
• 3.0 release notes
• 2.4 release notes
• 2.3.4 release notes
• 2.3.3 release notes
• 2.3.2 release notes
• 2.3 release notes
• 2.2 release notes
• Upgrading from 2.1.x and Django 1.2.x