> Hi devs, > > Since JV and I are at Javaone, Thomas Mortagne has kindly accepted to > become the release manager for XE 1.4RC1. > > I've quickly reviewed the jira list of outstanding issues and I think > the following should be fixed before the RC1 release: > http://jira.xwiki.org/jira/browse/XWIKI-2274 > http://jira.xwiki.org/jira/browse/XWIKI-1809 > > Also we need to verify that the Lucene plugin works fine and doesn't > throw any error when we start XE and leave it running for a few > minutes as it used to do (I think Sergiu fixed this). > > Anyone knows of any crucial outstanding issue for 1.4RC1? Note that > RC1 means that it's a release candidate for being promoted to 1.4 > final in a few days if its stable enough.
Not really an outstanding issue but... I am planning to have the next XWatch release based on XWiki 1.4 and, because of GWT's problems with browser standards mode rendering, I need a method to remove the document type declaration in the standard xwiki pages. The simplest solution would be to add a parameter to handle the declaration in htmlheader.vm. Now, since Watch is deployed as a xar, I cannot do that watch-specific and I need it in platform-web. The specific issue bothering me is at: http://jira.xwiki.org/jira/browse/XWATCH-104 . WDYT? Is it ok to allow the users to request a page with a specific doctype? Is it ok to do it this way? (the cleaner solution, but harder to implement, would be to have the doctype specified at content render time e.g. $response.setDoctype("standard")) If all above true, can we have this in 1.4? Happy coding, Anca Luca > > The release was planned for last Friday so we need to set a new > release date (tomorrow would be great). I'll let Thomas propose a date. > > Thanks > -Vincent > > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
