Skip to content
ojii edited this page Feb 1, 2011 · 22 revisions

django CMS 2.2 roadmap

Timeline

With 2.2 we target a 3 month release cycle. In order to keep that tight schedule we define a date for feature definition freeze and for when we close the merge window.

The feature definition freeze will happen on February 28th, 12pm (noon) Swiss time.

The merge window will close on March 31st, 12pm (noon) Swiss time.

Feature definition freeze

The feature definition freeze is the date when we will stop accepting new feature proposals and definitions for 2.2. Any feature proposed (or implemented) after this date which has not been accepted by the community and the core developer team will not be merged into 2.2.

Merge window

The merge window is the time period in which we will merge features into the main repository. For features to be merged, they have to be in a fairly mature state, well unit tested and documented. Once the merge window closes, no new features will be merged into the main repository. This of course also applies to features accepted for 2.2. Features which were accepted but are in an unsatisfying state when the merge window closes will be bumped to the next version.

Feature list

Features proposals should be sent to the django-cms-developers mailing list and be discussed there. A core developer will then add it to this list.

Backend improvements

Description: Improve backend administration interface for CMS Pages. See http://mixedcase.nl/articles/2011/01/29/django-cms-backend-usability/
Discussion: https://groups.google.com/forum/#!topic/django-cms-developers/aqRo88yiUtY
Status: Pending
Mentors: Kevin Renskers (mixedCase)
Branch: Not available yet

Multi Host capabilites

Description: Adding support for https://github.com/jaddison/django-multihost to the CMS.
Discussion: https://groups.google.com/forum/#!topic/django-cms-developers/1iduLdfwBXQ
Status: Pending
Mentors: Aziz Bookwala
Branch: Not available yet

Option to exclude pages from URL generation

Description: There should be an option to exclude pages from URL generations. So a page 'world' under the page 'hello' which is flagged to be excluded would have the URL '/world/', not '/hello/world/'.
Discussion: https://groups.google.com/forum/#!topic/django-cms-developers/xEmx0AsRdzo
Status: Pending
Mentors: Ulrich Petri
Branch: Not available yet

Use django-mptt as a proper dependency

Description: django-mptt should become a proper dependency for the CMS instead of being shipped with it.
Discussion: https://groups.google.com/forum/#!topic/django-cms-developers/FzuXkOgW1ek
Status: Merged
Mentors: Jonas (ojii), jalaziz
Branch: Merged

Remove django-dbgettext support

Description: Remove support for django-dbgettext for page slugs and other translatable fields, including plugins.
Discussion: https://groups.google.com/forum/#!topic/django-cms-developers/teWlNy3_Bto
Status: Accepted
Mentors: Jonas (ojii)
Branch: Not available

Multi-device-support

Description: Support for multiple devices. The clear specification is still being discussed about.
Discussion: https://groups.google.com/forum/#!topic/django-cms-developers/KTueGL9GJgw
Status: Pending
Mentors: Jonas (ojii)
Branch: Not available

Deprecate PlaceholderMediaMiddleware/plugins_media in favor of django-sekizai

Description: I propose deprecating the hacky and buggy PlaceholderMediaMiddleware (and plugins_media) template tag in 2.2 in favor of django-sekizai and removing it in 2.3. In 2.2, all core plugins should be changed to use django-sekizai (using 'js' and 'css' sekizai namespaces as convention), the plugins should internally all fall back to populate the 'cmsplugins-media' sekizai namespace using the existing python APIs to add media, plugins_media should then be a de-facto alias for 'render_block "cmsplugins-media"'.
Discussion: https://groups.google.com/forum/#!topic/django-cms-developers/OiplObxBGa4
Status: Pending
Mentors: Jonas (ojii)
Branch: Not available

Include page level in page unicode method

Description: I'd like to propose that we add back in the page level to the page unicode method. This is incredibly helpful when using the link plug-in and selecting a page. I have a site with over 500+ pages and without some indication of the level it would be impossible to pick a page.
Discussion: https://groups.google.com/forum/#!topic/django-cms-developers/1Ndpa_wwxUM
Status: Pending
Mentors: Andrew Schoen
Branch: Not available
Clone this wiki locally