looks good. One point: I notice that the SearchQuery interfaces have been copied to the bridge. But the only implementations of these interfaces work with core objects, and not mmci objects. Shouldn't that be addressed as well in this release?
ernst > -----Oorspronkelijk bericht----- > Van: Pierre van Rooden [mailto:[EMAIL PROTECTED] > Verzonden: donderdag 24 juni 2004 16:26 > Aan: [EMAIL PROTECTED] > Onderwerp: Releaseplan 1.8, v2 > > > Below is another proposal for the MMBase 1.8 release plan. > I made only a few changes to the original, mostly in clarifications. > Please provide your response to this proposal. > In a week time I will post a final version to vote over. > > > > =================================================================== > 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 separate 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 module 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 (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 > > - 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 > - Mark xerces/xalan dependent code for future change (there is no > solution for this dependency yet) > - cleaning of the html-dir > > III Improvements > > The following Core functionality will be evalued and (if needed and > possible) improved in 1.8. 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 > - 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. 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 > - Running on packaged 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 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. > > - Cleaning Project, fase II (see above) > - Distro project > - Field types project > - Richtext project > - Taglib II project > - Packaging project (new) > > VI Other > > - update and improve documentation > ! > -- > Pierre van Rooden > Mediapark, C 107 tel. +31 (0)35 6772815 > "Never summon anything bigger than your head." > >
