Development Roadmap
From OpenCms Wiki
(Difference between revisions)
Cschoenfeld (Talk | contribs) (Added a link to the mailing list archiv at Nabble.com) |
|||
(17 intermediate revisions by 9 users not shown) | |||
Line 1: | Line 1: | ||
− | + | ;Releases Schedule: | |
+ | * Version 8.0: Q4, 2010 (from Conference Opening Keynote, OpenCms Days Conference, June 15-16, 2009: [http://www.opencms-days.org/export/sites/opencmsdays/en/program/slides/k1.pdf]) | ||
+ | |||
+ | == Preliminary Plan for Version 8.0 == | ||
+ | based on Conference Opening Keynote, OpenCms Days Conference, May 15, 2009 and current development status: | ||
+ | |||
+ | OpenCms 8.0 will focus on content manager usability improvements: | ||
+ | *Introduction the “Advanced Direct Edit” (or ADE) mode | ||
+ | **With ADE, Content managers will be able to do the most common tasks from the “Direct Edit” interface and not be required to use the workplace | ||
+ | |||
+ | *Improved Semantic Web Functionality | ||
+ | *Content subsription and tracking engine | ||
+ | |||
+ | OpenCms 8.0 optional planned core and API improvements: (Subject to change) | ||
+ | * JPA integration for g supporting multiple Databases | ||
+ | * Scripting language support | ||
+ | * Workflow integration | ||
+ | * Repository Standards compatibility | ||
+ | |||
+ | |||
+ | This version is expected to use JDK 6 or later. |
Latest revision as of 09:55, 8 July 2010
- Releases Schedule
- Version 8.0: Q4, 2010 (from Conference Opening Keynote, OpenCms Days Conference, June 15-16, 2009: [1])
Preliminary Plan for Version 8.0
based on Conference Opening Keynote, OpenCms Days Conference, May 15, 2009 and current development status:
OpenCms 8.0 will focus on content manager usability improvements:
- Introduction the “Advanced Direct Edit” (or ADE) mode
- With ADE, Content managers will be able to do the most common tasks from the “Direct Edit” interface and not be required to use the workplace
- Improved Semantic Web Functionality
- Content subsription and tracking engine
OpenCms 8.0 optional planned core and API improvements: (Subject to change)
- JPA integration for g supporting multiple Databases
- Scripting language support
- Workflow integration
- Repository Standards compatibility
This version is expected to use JDK 6 or later.