On 18/12/2006, at 5:01 PM, Alex Thurgood wrote:
For now, I suggest that we abandon any release timeline, freeze the product feature wise and start fixing the problems we have encountered.There speaks a man after my own heart. It's encouraging to hear echos of what I've mentioned on other lists previously. However, I fear that our voices be drowned in the sea of developers that actually do the coding and wouldn't get to see their pride and joy out among the public. This issue has been discussed before, certainly by the CC, and possibly also on this list (from memory). But I certainly second James' and Clytie's concerns.
It has recently been discussed on the releases list.If this issue doesn't achieve change, I am willing to boycott three- monthly releases.
I will release 2.1, then will not release again until 2.3, after a minimum of 6 months, and only if I'm satisfied with the quality of our product.
I will publicize this situation in OOo, in my language community and throughout the open-source community. I am not interested in quantity: I work for quality.
I believe my users deserve our best efforts. I would be personally ashamed to release a build with any significant bugs.
I strongly support James' statement in his recent email to the releases list. He speaks from experience, with the best interests of OpenOffice.org at heart, and his work in QA in the mac-porting project sets an excellent example for new participants.
I also suggest running some BSPs (Bug-Squashing Parties", both locally and via IRC. They work well, get a lot of volunteers involved, and deal with a really impressive number of bugs in a short time. You could even include some friendly competition between BSPs. ;)
Make fixing issues a priority for a month or so, publicize it widely, have a counter on the main page, have teams and friendly competition. There's a lot we can do, but we need the time to do it, before releases. Release OpenOffice.org 2.2 in June 2007, and we'll make it a product that stands tall with its competitors.
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do)
http://groups-beta.google.com/group/vi-VN
PGP.sig
Description: This is a digitally signed message part
