Hi,
On 19 Dec 2006, at 05:16, Clytie Siddall wrote:

In fact, a bug which might take only half an hour to fix can drive away users attracted by a feature created by months of developer effort.

+1


Bug-fixing and QA in general needs more priority.

Talking from a builder perspective on the Mac Intel platform [1], the code recently has got worse. Master workspaces no longer compile out of the box. They need to be patched and that simply isn't good enough. I have tried compiling child workspace that are marked as new, but they will sometimes fail due to the fact that they are synced against an old master workspace that is broken. Some of them are not even being worked at the moment, and there is no easy way to know that. As far as I understand, a CWS marked as new should be ready to be integrated.

I have basically given up trying to compile ooo using the buildbot due to the above noted continual failures.

I would like to see more testing for CWSes BEFORE they get integrated into a MWS. If any developer is looking for their CWS to be tested on the Mac, just drop me a mail. At the moment, I can do it within a week or so. Though it may be completed a lot earlier. If you give me a heads up warning that you will be wanting the CWS tested, I can plan ahead.

The buildbot infrastructure has been useful in the past, as CWSs have been tested on other platforms that the developers don't have access to and problems fixed. This is the whole point of the buildbot infrastructure. I want to see it being used so that we can have a higher quality of code, with errors being caught at an earlier stage in the development cycle. Most importantly build errors are not passed into the Master workspaces. If developers do NOT use the buildbot infrastructure, YOU ARE going to LOSE it. I personally don't want that!


[1] http://termite.go-oo.org/MacPort1  http://termite.go-oo.org/

Shaun

Send instant messages to your online friends http://uk.messenger.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to