-
Notifications
You must be signed in to change notification settings - Fork 1
2.2 roadmap
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.
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.
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.
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.
| 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 |
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.
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.
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.
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.
| 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 |