Hello,
There are only a few weeks left before the final 1.1 release. There
has been a lot of work put in this release (although even more work
was needed), and we've already started working on the first 1.2
milestone.
Past
A short summary of the closed issues thus far:
- 215 issues in xwiki-platform (102 bugs, 81 improvements, 15 new features)
- 32 issues in xwiki-enterprise
- 15 issues in panels-application
So this was mainly a bugfixing release, which means that now we have a
more stable platform, and an enjoyable default wiki. There have been
very few new features, as there was not enough manpower. The best
achievement in my opinion is the new build architecture, with the
platform separated from the default wiki, and internally separated
into several modules (core, web, plugins...).
Present
If everything goes right, we still have two more RC releases before
the final 1.1. These should not contain any changes (
http://en.wikipedia.org/wiki/Release_candidate#Release_candidate ),
but only critical fixes. That's why we should stop committing things
in the 1.1 branch, unless it is a critical bug fix.
In order to be able to make a proper release on the 27th, I'd propose
a code freeze on the 1.1 branch at 6 A.M. GMT 26th of August, with
everybody giving a hand on testing on sunday, and a quick release on
monday.
Future
We started with a list of expectations (
http://www.xwiki.org/xwiki/bin/view/Idea/FeaturesFor11 ) which was
only in very small parts covered, mostly because we concentrated on
bufixes. The good news is that we'll be able to concentrate on new
features from now on, and we can hope that most of these goals will be
covered in the 1.2 release.
However, there are still 162 issues marked as bugs in the platform (of
which 39 in the core), so there's still work on bugfixing.
The current WYSIWYG editor is cracking; every new fix/feature causes
another thing that was working before to fail, and we don't have
enough tests for the moment to automatically detect this. The
complexity is increasing, which makes the editor unusable on slow
systems or for large documents. With Nam leaving, we won't have a
person that knows the code well to take his place. This is why we must
concentrate on the new GWT-based editor (
http://www.xwiki.org/xwiki/bin/view/Idea/WikiModel+and+GWT+Wyswiyg+Architec…
) and hope that in 3 months we'll have a fully functional editor.
Another direction would be the component-based architecture. Vincent
already committed a proof-of-concept in
xwiki-sandbox/xwiki-components, which looks good, but contains very
few things. It seems easy to write in this manner, so we should try
and have a working core based on this architecture.
Thanks to all that contributed to the 1.1 release,
Sergiu
--
http://purl.org/net/sergiu