We originally planned to publish a series of unstable releases in the 1.3 series. However, there has never been a real release in 1.3 (unless you count the "preview" releases which were created by Dannes from time to time) and people started using SVN trunk in production instead. This is ok, but it gets problematic if we want to integrate some of the pending branches which will probably destabilize trunk for a while.

We thus suggest to release the current trunk as a stable release. This means to skip 1.3 and the new releases has to become 1.4 while SVN trunk becomes 1.5.

For final testing, a release candidate will be published for 1.4 and should be out for at least 4 to 6 weeks before the final can be released.

Todo for 1.4

To be completed

• Lucene index documentation, further testing, switch documentation search to Lucene
• Versioning extensions: documentation missing
• XQueryURLRewrite: documentation missing

Other

• Drop default full text index: it needs lots of caching memory and can have a destabilizing effect. New users typically don't turn it off, so we think it's better to disable it by default. For the future the builtin ft index will be deprecated and replaced by the new lucene-based implementation. An exception should be thrown if no full text index is defined on any collection in the db and a full text extension is used.
• Set default XQuery watchdog max document size to -1 in conf.xml
• Add version numbers to exist.jar, exist-modules.jar ...
• Remove Cocoon from the standard distribution
• Fix and test the lucene module

Minor Things which could go into 1.4

• Create XSL:FO stylesheet to produce a PDF version of the documentation. This should mainly serve as an example.
• Rewrite Roadmap. Most of the items on it have been completed. The new roadmap may better be placed on the wiki. It should help new users to find projects they want to contribute to. Add categories like "difficulty level" or "estimated time frame".
• Reorganize the function documentation. Maybe move it out of the Java classes and into a proper documentation system, e.g. FuncX.
• Update Jetty 5 to 6