1.1   Version 0.1

• Compatibility mode for standard CPS pages, i.e., based on main_template
• File system theme container (reads a configurable path, relative to INSTANCE_HOME)
• No theme and page negociation (container's default/index.html)
• (c)ElementTree engine

1.2   Version 0.2

• Included in CPS-3-full bundle.
• Documentation for CPSDesignerThemes developers
• engine refactoring and lxml engine
• CPSSkins themes conversion
• Ships with exported version of CPS 3.4 default theme
• theme and page negociation

1.3   Version 0.3 (quality milestone)

• Stabilisation of engine API and extensive unit testing.
• Overall robustness.
• Effort towards leverage of Zope component architecture where relevant, with future releases in mind
• documentation for designers
• Early adopters can start prototyping projects with the product

1.4   Version 0.4

• CPSDesignerThemes based portlet editor.
• No more dependencies on CPSSkins. Can run without the portal_themes tool, but can also coexist.

1.5   Version 0.5 (quality milestone)

• Documentation for integrators, notably upgrade scenarios from CPSSkins
• Suitable for pre-production by early adopters
• Full iso-functionality with themes exported from CPSSkins.

1.6   Version 0.6

• ZODB local themes with zip upload
• much care to test that reverse proxying down inside the portal works
• HTTP header negociation

From 0.6 on, as much point releases as necessary to reach

2.1   Version 1.1 (CPSDefault integration for 3.5)

These are actually CPSDefault features, but that of course means that CPSDesignerThemes is ready for them

• Conversion from CPSSkins themes as an upgrade step
• CPSDefault's base profile switches to CPSDesignerThemes for next 3.5 release
• Ships with an original CPS 3.5 theme
• CPSDesignerThemes stays optional in the 3.4 branch

2.2   Version 1.2

Optimization round-up. This is postponed so late because early tests suggest that an lxml based themes engine will run in epsilon time compared to the rest of CPS.