Charlie Clark wrote:
Maho's builds are a great resource for anyone following the project with anything more than a passing interest and in a great tradition of "nightly builds". Yes, they might be unstable so we don't rely on them but we know that.
Yes, but for people who are not following the project with more than a passing interest?
Certainly, *we* expect that the builds could be unstable, but what about J. Random Blogger who downloads the latest snapshot (more or less at random) to look at the native Aqua of OO.o 3.0 beta and sees these apparently random crashes? Now, J. Random goes back to his blog and announces to the world, OO.o Aqua is crap, better go with Neo.....
Eric's point is that having unstable code available to the general public who may expect more from the code, and who may not really understand that these snapshots are unstable, is detrimental to the good will of the Aqua project, and to OO.o in general. From a public relations point of view, the current situation is very nearly a disaster.
As Eric has said, people not initiated in the project's arcana might just expect these builds to actually work for more than 5 minutes without crashing, in fact they might expect them to be very stable and nearly feature complete.--They are "public" builds/releases after all.
I'm in no way knocking Maho or the great work that he does, but I do agree with Eric that Maho does not have to provide every milestone (and perhaps should not), and that it would be a good idea if he could wait until development and QA think they have a usable build before posting to the net at large.
Cheers, Jason --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
