Development & community

django CMS is an open-source project, and relies on its community of users to keep getting better.


You can join us online:

You can also follow:

You can also follow:

You don’t need to be an expert developer to make a valuable contribution - all you need is a little knowledge of the system, and a willingness to follow the contribution guidelines.

Remember that contributions to the documentation are highly prized, and key to the success of the django CMS project.

Development is led by a team of core developers, and under the overall guidance of a technical board.

All activity in the community is governed by our Code of Conduct.

Security issues


If you think you have discovered a security issue in our code, please report it privately, by emailing us at

Please do not raise it on:

  • IRC
  • GitHub
  • either of our email lists

or in any other public forum until we have had a chance to deal with it.

Release schedule & policy

The roadmap <>`_ can be found on our GitHub wiki page.

We are planning releases according to key principles and aims. Issues within milestones are therefore subject to change.

The django-cms-developers group serves as gathering point for developers. We submit ideas and proposals prior to the roadmap goals.

We officially support the current and previous released versions of django CMS. Older versions are maintained through the community. Divio provides long term support (LTS) through commercial support.

Branch policy

  • master: this is the current stable release, the version released on PyPI.
  • support/3.2.x: this will be our next stable release; this is the most appropriate branch for fixes and patches that will go into the next master
  • develop: this will be django CMS 3.3; this is the most appropriate branch for more substantial features that will need team co-ordination

If in doubt, ask on the #django-cms IRC channel on freenode or the django-cms-developers email list!