It's already an improovement that we have a releaseplan before making the distribution ;-) I also would like to discuss this releaseplan at the MMBase developers meeting. But i think this plan is a very nice start.
Rob
Pierre van Rooden wrote:
Below you will find a first attempt at a 1.8 release plan. Release 1.8.0 will be directed not so much at adding new functionality, but on improving and cleaning existing code. Some of the initiatives mentioned below will be done in the form of small MMBase projects witha specifioc aim (i.e. a MultiCast II project). Please read through this, and indicating if you find anything missing, anything that seems inaccurate or unrealistic, or any other comments. I also think it worthwhile if we discuss this release plan on the upcoming developer meeting.
========================================== MMBase 1.8.0 - Release Plan ========================================== TODO for 1.8.0 release of MMBase:
I Core/Project abstraction
The following applications should be removed from the core and moved to a speparate application:
- SCAN, including the org.mmbase.module.gui.html.* classes and supporting util classes (i.e. scanpage) This includes removing SCAN specific hooks from some core classes - Email application: find a solution for the email module class interface that is now in the core - Config mdoule and org.mmbase.config: xml parsers and color coders (perhaps a rewrite is better?) - Tools: move utility classes, modules, and builders that are still useful to a tools application
II - Cleaning
The following steps should be made to clean the code. Note that part of this is also done during abstraction
- removing all old database support en storage classes - remove all utility classes, modules, and builders that are no longer used, i.e. DateSupport or Storable - Removal of xerces/xalan dependencies (if possible) - cleaning of the html-dir
III Improvements
The following Core functionality will be evalued and (if possible) improved in 1.8 :
- Multicast: select an appropriate (or pluiggable) communication system, slve issues with bursts of change events - Modules and Builders: implement a proper way for loading, unloading, reloading, and shutting down modules and builders - Security: field-level security checks
IV Performance and Maintenance
Performance issues should be analyzed and if possible resolved. Performce and maintenance related issues are:
- Monitoring of MMBase performance issues, i.e. profiling - Running on packed war (xml configuration as resources) - serving images staticly - related-nodes optimalisation (passing queries to parent) - create a better build-process
V Projects
The following projects should be finished
- Cleaning Project, fase II (see above) - Distro project - Field types project - Richtext project - Taglib II project (treetag) - MMCI 1.2 Project, fase II (Administration classes)
VI Other
- update and improve documentation
