Why django CMS' Next Version Will Be 5.0

Feb. 27, 2025

Version numbers tell a story of progress and change. For django CMS, the jump to 5.0 reflects major improvements and a commitment to clear, stable updates. But why skip 4.2? It all comes down to semantic versioning and breaking changes.

In the dynamic world of software development, versioning plays a pivotal role in conveying the evolution and compatibility of a project. For django CMS, a robust content management system built on Django, the journey from version 3 to the anticipated version 5.0 has been both transformative and insightful.

The Evolution to Version 4

Several years ago, a dedicated team embarked on a mission to elevate django CMS to an "enterprise-ready" platform. This initiative, internally dubbed "version 4," aimed to enhance efficiency, expand feature support, and introduce flexible functionality. The project culminated in the official community release of django CMS 4.1 on December 31, 2023. A hallmark of this release was the introduction of a comprehensive content versioning system, empowering users to track and manage changes seamlessly.

The Versioning Dilemma

As development progressed, the community faced a versioning conundrum. The term "version 4" had become synonymous with a significant overhaul, representing a new era for django CMS. This association led to challenges in adhering strictly to semantic versioning principles, especially when contemplating subsequent releases that introduced breaking changes. The dilemma was whether to increment the major version number, signaling these changes, or to redefine the versioning strategy to reflect the core state of django CMS.

In late 2024, discussions intensified around the upcoming release, initially envisioned as version 4.2. However, the inclusion of breaking changes, such as the simplification of models to boost performance, necessitated a reevaluation. While transparent to the vast majority of django CMS-based projects, there might be the need for code adjustments if projects directly access django CMS' internals. Adhering to semantic versioning the community reached a consensus: the next release would be designated as django CMS 5.0. This decision not only aligns with best practices but also provides clarity to users regarding the nature and impact of the updates.

Implications for the Ecosystem

Despite the jump to version 5.0, upgrading remains straightforward. The version number change reflects structural improvements, not an as radical departure from previous releases as version 3 to 4 was. Users can upgrade automatically using standard Django migrations, with the usual precautions like database backups to ensure a smooth transition.

With this decision, django CMS' Long-Term Support (LTS) table now looks like this. The alignment of major version numbers of Django and django CMS is a current coincidence and we expect depatures in the future.

django CMS	Python version					Django version
	3.13	3.12	3.11	3.10	3.9	5.2	5.1	5.0	4.2	4.1	4.0
5.0.x	✓	✓	✓	✓	✓	LTS	✓	✓	LTS	×	×
4.1.x	✓	✓	✓	✓	✓	✓	✓	✓	LTS	✓	✓
3.11.x	×	✓	✓	✓	✓	×	✓	✓	LTS	✓	✓

Looking Ahead

As django CMS approaches the release of version 5.0, the focus remains on delivering a platform that balances innovation with stability. For the future we expect major version bumps such as to 6, 7, and so on to become much more common. To navigate the ecosystem more easily, we are in the process of providing a single point of truth for compatibility of all endorsed packages.

For us, this journey underscores the importance of adaptable versioning strategies, and thank you for welcoming django CMS 5 soon.