django CMS 3.7 Release Candidate 2
Release Candidate 2 for django CMS 3.7 is now available.
The second release candidate for django CMS 3.7 is now available and brings with it support for Django 2.2. Django 2.2 is designated as a long-term release which means it will receive security updates for at least three years.
django CMS 3.7 will be the next major LTS release of django CMS, replacing django CMS 3.4 LTS, which has been receiving updates since 2016. django CMS 3.4 LTS will continue to be supported until Django 1.11 LTS reaches the end of support in April 2020.
Important to note is that Django 2.1 (supported from django CMS 3.6) will not recieve updates after December 2019 therefore we strongly recommend preparing to update to django CMS 3.7 and Django 2.2 if you are not using django CMS 3.4 LTS.
Evaluating django CMS 3.7 Release Candidate 2
If you have already updated to django CMS 3.6 then you should find the transition to Django 2.2 straightforward. You can find breaking changes between Django 2.1 and 2.2 in the Django release notes.
If you are migrating from Django 3.5 or earlier (Django 1.x) then we recommend following the Django upgrade guide and reviewing your add-ons accordingly. The release candidate can be used to test against and prepare for migration.
Divio Cloud installation
The easiest way to try out django CMS is by creating a new Divio Cloud project, which takes only a couple of minutes.
In the Divio Cloud Control Panel, create a new django CMS project.
Once it has been created, configure its Addons. You will need to specify:
- django CMS: select version
3.7.0.5
or newer from the Alpha channel of Aldryn django CMS
Then you can Deploy the project.
Install django CMS using pip
Run pip install django-cms==3.7rc2
. You should find that updating django CMS to 3.7 in a project already running 3.6.x requires no other changes, as long as you're using compatible versions of Python and Django, and have stopped using deprecated APIs.
What's new
Please see the django CMS 3.7 release notes for more information about what's new and how to upgrade.
We want your feedback
Your feedback is vital and warmly welcomed! All reports, positive and negative, are valuable to us. For technical issues, please use GitHub issues.
blog comments powered by Disqus