On 7 Oct 2010, at 13:35, Ross Gardler wrote: > On 07/10/2010 13:10, Scott Wilson wrote: >> On 6 Oct 2010, at 11:45, Ross Gardler wrote: >> >>> On 06/10/2010 10:57, Kris Popat wrote: >>>> Hi All, >>>> >>>> I've spent some time going through the apache release process and going >>>> through wookie itself. I think I've got the process straight but mentors >>>> please keep me right on this. Some or many of these processes may >>>> already have been done or started. Here is an outline list of what I've >>>> extracted from the documentation that Ross pointed me towards (thank you >>>> Ross) and other docs on the apache site. >>>> >>>> >>>> Analyze Open Issues - as a community we need to decide which issues and >>>> bugs can/must be resolved for this release and which we may postpone for >>>> future releases. >>> >>> We can all help here. >> >> We also need to Resolve the Closed issues against 0.8.1 - as I closed quite >> a few of them I shouldn't verify them myself. > > I suggest we do that as part of the test cycle. It will ensure that at least > one person has conducted fairly rigourous tests.
Yes - and to Verify an issue we should document how it was tested (and preferably, add JUnit tests to do it automatically in future.) >> Once we've done that there will be only 8 issues left to decide on. > > Cool. I wonder if you could post their subjects here and your proposal. In > most cases I suspect we'll just +1 what you propose ;-) 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. 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. 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? 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. 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) WOOKIE-90 JQuery document ready function not working This affects widget developers now, so if possible we should try to fix this. 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. (NB I've assumed the release we're doing now is 0.8.1 and therefore a future release would be 0.8.2.) > > Ross
