On Mar 20, 2009, at 6:48 PM, Sergiu Dumitriu wrote: > Vincent Massol wrote: >> Hi devs, >> >> XE 2.0 >> ===== >> >> We've had discussion about XE 2.0 in the past. I think now is the >> right time to release it and we should prepare to do so. Two reasons; >> 1) We've had a lot of new features (new rendering, new wysiwyg, >> webdav, REST, office import, usability improvements, etc) added >> recently in 1.8 and this alone warrants calling it 2.0. The new >> rendering and new wysiwyg could be set as default in XE 2.0. >> 2) XE 1.0 marked a stability level. XE 2.0 will mark another >> stability >> level (I'm thinking about the old wysiwyg editor which could be said >> to be stable...) >> 3) It's been almost exactly 2 years since we released XE 1.0, it's >> high time for a major release. >> >> However since we still have a bit of work to fully finish the new >> rendering and new wysiwyg and since we want user feedback from 1.8 to >> ensure we get a rock solid 2.0 release I propose to have a XE 1.9 >> release before the XE 2.0 (which would be a promotion of XE 1.9 final >> with the config change to have new syntax/wysiwyg as defaults). >> >> The other advantage of releasing XE 2.0 is that we want to start the >> maintenance period for the old rendering/old wysiwyg as early as >> possible to get new people to use the new system. Once 2.0 is >> released >> we'll continue releasing bugfix versions of 1.9.x from time to time >> but we'll advise people to switch to 2.x. I propose we keep support >> for the old 1.0 syntax (either using the old code or using the 1.0 >> --> >> 2.0 syntax converter) for 1 year. This is the time we have to make >> our >> existing users switch to the new syntax. Note that with the automatic >> converters it shouldn't be something too difficult. >> >> Roadmap for XE 1.9 >> ================ >> >> General:It's a stabilization release meaning we must resist putting >> new things in it and fix what doesn't work well enough. >> >> Content proposal: >> * Finish/stabilize/document new rendering - Thomas/Vincent >> * Finish/stabilize/document new wysiwyg editor - Marius/Anca >> * Finish/stabilize/document office importer + doc splitter/management >> - Asiri >> * Finish/stabilize/document webdav - Asiri >> * Finish/stabilize/document REST support - Fabio >> * Finish/stabilize/document new blog application - Sergiu/Guillaume >> * Continue UI improvements (ex: new treeview, new search interface, >> full list to be defined) - JV/Ecaterina/Guillaume >> * Fix search using lucene plugin - ???? >> * Finish XE French translations - JV/Guillaume >> * Fix other bugs (watchlist, page names with special chars, etc) - >> All >> * Refactoring of apps to use more of SSX - Jerome? > > I think it is important to finally do some profiling and improve the > bottlenecks. One thing that's been causing a lot of problems is the > attachments storage that's a memory hog. Another is excessive > cloning of > XWikiDocument objects, which should be improved by both improving the > clone performance and reducing the number of clones created. > >> Note: I don't think we can commit to have a new skin system or a new >> skin in place for the 1.9 timeframe. >> >> Proposed Dates: >> * 1.9M1: 6 April >> * 1.9M2: 4 May >> * 1.9RC1: 18 May >> * 1.9RC2/Final: 1 June >> * 2.0: 15 June > > As always, I'd like a bit more time between 1.8 and 1.9M1, but I'll go > with the majority.
You can consider 1.9M1 has been started for 2 weeks already since 1.8 final was planned 2 weeks ago initially... :) My initial roadmap for 1.9 final was 2 weeks earlier but I've delayed it by 2 weeks to account for the slippage in XE 1.8. Thanks -Vincent _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
