done in a short enough amount of time. I have helped a bit with the statusbar work; I completed as much as I knew to do and need input for what to do next.
Bug 945735 still stands, and this is what matters here.
Also I'll need time to document the major new things in tutorials. This
also
needs time. And I want to do more redrawing cursors and icons, which is cosmetics but also important.
If there are people interested in / able to help with this work, would it be something you could farm out to them?
If someone comes up with something good, sure, I'll say thank you :) Otherwise I think it will just take me as much time to explain what I want to see as to actually do it.
We do have nightly autopackages posted at http://autopackage.org. If people could use that it would kill two birds - first since then we don't have to set up another nightly autobuild process yet, second so we can get some additional testing of autopackage itself. I'll take the task of encouraging people to use this approach.
That's good if it works. I didn't know about it. I think it needs more advertising.
If I recall correctly, the issues that caused the need for the .1 release were due to insufficient change control; non-trivial code changes were being checked in at the last minute, and one or two of these changes introduced serious bugs. So I agree we should announce our unofficial betas earlier and wider, but I think to prevent the causes of the .1 release last time what we really need is a firmer code freeze especially in the last couple days prior to release. What do you think?
Tighter freeze would be good but difficult as you know :) And anyway wider testing could make these last-minute changes unnecessary by uncovering the problems eariler.
_________________________________________________________________ Add photos to your e-mail with MSN Premium. Get 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI...