On 7 Oct 2010, at 18:26, Paul Sharples wrote: WOOKIE-67 Implement localization of widgets on per-instance basis -> >>>> WOOKIE-93 Implementing charset selection for start files This is the >>>> last remaining peace of the localisation issue - dynamic charset >>>> overrides by widget start files. However its not a blocker for a >>>> release as we try to serve everything as UTF-8 by default, so I >>>> suggest moving it to 0.8.2. >>> +1 >> +1 > + 1
DONE >>> WOOKIE-19 Write server admin guide We have a doc review as part of >>>> the release process, so I suggest we close this once we're past that >>>> step. >>> +1 >> +1 > + 1 OK >>>> WOOKIE-44 Default widget returns js "error" when loaded into a >>>> browser This directly affects users on IE8/9, so we should fix this >>>> now. Paul had already started the investigation on this, so may be >>>> able to provide a fix? >>> >>> Lets not delay the release for this, but instead make sure it is clearly >>> documented (ideally the widget will do a browser detection and report the >>> problem linking to the issue - maybe we'll get a patch). >>> >> >> If the fix for this is quick then it would be good to get it done. However, >> if it may take a little longer I'm in agreement with Ross >> > One way could be to add the browser detection for IE8 to the > wookie-wrapper.js and report the problem from there, that way all widgets > will handle the issue in the same way. I'll look into it. > BTW: I've been hacking around with IE9 beta and initially at least, it looks > as though this problem has been resolved (although i need to test it more > thoroughly). Pity its still a beta - most users won't yet have it. OK, over to you on this one! >>>> WOOKIE-119 Author info does not support bidirectional text There is >>>> basic support at the parser level; in practice you can use UTF-8 >>>> control characters now anyway - this adds more control in markup >>>> (e.g. for combinations of LTR and RTL text). I don't however see this >>>> as a release blocker, and we can fix this in 0.8.2. >>> +1 >> +1 > + 1 DONE >>> >>>> WOOKIE-111 Enable support for virtual hosts This is something we >>>> should look at, but it potentially touches a lot of areas of the >>>> server and configuration and needs a lot of testing. I'd opt to >>>> postpone this one to 0.8.2. (It's also entirely possible there are >>>> workarounds and we just need to document them) >>> >>> Another good one for us to document clearly in the readme. It sounds like >>> the kind of thing someone might just know how to do, lets ask for a >>> documentation patch. >> +1 > + 1 I've added a placeholder in the wiki and pointer to it from the README, and moved the issue to 0.8.2 >>>> WOOKIE-90 JQuery document ready function not working This affects >>>> widget developers now, so if possible we should try to fix this. >>> >>> There is a workaround for this. Lets document it in the readme and get the >>> release out. If someone gets a patch in before the code freeze then all the >>> good, but this is the kind of thing that could indefinitely hold up a >>> release. >>> >> >> +1 > + 1 OK, added an FAQ entry for this and moved to 0.8.2. >> >> It might be an idea at this point to put a time line on the release process >> so those who might produce a patch know when as well as what (this may apply >> to other issues). If we are aiming for ApacheCon NA then we have about 3 >> weeks for the whole process - giving some time for propagation through the >> mirrors. I'll create a timeline based upon a modified release schedule >> (thanks Ross for the comments) and see how it looks. >> >>>> WOOKIE-81 Ensure all code has license headers This is part of our >>>> release process anyway, so we should close this once we've done our >>>> due diligence on licenses. >>> +1 >> +1 > +1 OK >>>> (NB I've assumed the release we're doing now is 0.8.1 and therefore a >>>> future release would be 0.8.2.) >>> >>> I wonder if we ought to make it a 0.9. There have been some significant >>> improvements since 0.8 (no MySQL, standalone mode, built in demos). The >>> issues above would therefore all be 0.9.1 issues. >>> >> >> I'm happy with that so >> +1 > + 1 +1 from me too. I presume there is some magic in Jira that will "make it so".
