On Mar 20, 2009, at 6:55 PM, Jerome Velociter 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 sure can help with this, but I'm not sure of what value it brings > for > 1.9. Potentially it can introduce some bugs, so I would rather do this > after XE 2.0 (same for a general refactoring of xwiki's javascript)
Yes you're right. This should not be a first level objective. We should focus on bug fixes as much as possible. > In the mean time, if we still agree we want it for 1.9, I am still > committed to write support for velocity/script wiki macro bridge. Yes definitely for that bridge. Thanks -Vincent > +1 for the general objectives of 1.9 and for the dates. > > Jerome >> >> 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 >> >> WDYT? >> >> Thanks >> -Vincent >> _______________ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
