Forgot your password?
New user?
Document Actions
#148: Move to CMF 2.1
Require CMF 2.1.
- Proposed by
- Hanno Schlichting
- Seconded by
- Alexander Limi
- Proposal type
- Architecture
- Assigned to release
- State
- completed
Motivation
CMF 2.1 uses quite some Zope3 technologies we are also going to move to. So by moving to this CMF version we will not only keep up-to-date with our underlying framework, but also gain more flexibility to reuse CMF functionality.
Assumptions
There will be a final CMF 2.1 release by the time we will ship our first beta release.
Proposal
Require CMF 2.1 for Plone and drop support for CMF 1.6. As a result CMF 2.0 will not be supported for any Plone release.
Risks
- Moving to CMF 2.1 might break Add-on products.
- We won't have a stable release of CMF in time.
Progress log
- Set-up a test instance based on the Plone 3.0 and CMF 2.0. Run all the tests and fix all cases where they break.
Participants
Hanno Schlichting
cross-communication to CMF list
Hanno, if you could make sure you also communicate and updates on this work item to the CMF list we could eliminate at least one risk factor ("no CMF release in time") and you can help shape CMF 2.1.
jens