===================================================================
                     MMBase 1.9.0 - Release Plan
$Id: release-plan.txt,v 1.7 2006/09/07 16:56:08 michiel Exp $
===================================================================

TODO for 1.9.0 release of MMBase:

I Core/Project abstraction

- Tools: move utility classes, modules, and builders that are still useful to a tools application
  (or in case this is too hard, tag them for inclusion in a later release)


II - Cleaning

The following steps should be made to clean the code. Note that part of this is also done during abstraction

- cleaning of the html-dir
  DO

III Improvements

The following Core functionality will be evalued and (if needed and possible) improved in 1.9.  It
is possible that actual changes are delayed to a later release if it proves too time consuming for
this one.

- Multicast: select an appropriate (or pluggable) communication system, solve issues with bursts of
  change events
  DO

- Modules and Builders: implement a proper way for loading, unloading, reloading, and shutting down
  modules and builders
  SKIP

IV Performance and Maintenance

Performance issues should be analyzed and if possible resolved. It is possible that actual changes are delayed to a later release if it proves too time consuming for this one.
Performance and maintenance related issues are:

- Monitoring of MMBase performance issues, i.e. profiling
  DO?

- serving images staticly
  DO?

- related-nodes optimalisation (passing queries to parent)
  DO?

- create a better build-process
  DO.  maven?

V Projects

The following projects should be finished or brought in a stable state.
This is dependent on input from the project manager.
New projects that are not in a stable state will not be deployed in the 1.8 release.

- Component Frame Work

- Cleaning Project, fase II (see above)
  PENDING
- Data types project
  DONE
  ----> DO Review code and new methods (org.mmbase.bridge.*, org.mmbase.datatypes.*)

- Editwizard 2
  SKIP?

VI Other

- update and improve documentation
  DO

- testing
   - junit tests must succeed

   - junit tests must be reviewed

   - other test areas