Eric Hoch wrote:
Hi Shaun, James,
Am Tue, 25 Mar 2008 20:19:57 -0700 schrieb James McKenzie:
Shaun McDonald wrote:
Hi Mac Port testers,
With OpenOffice.org X11 2.4 due out tomorrow, what is the status
of the testing?
The Danish community have approved a build on linux.cz, that
uses the file naming convention to show that it is an Aqua build.
<http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/680/OOH680_m12/Build-1/OOo_2.4.0_080316_MacOSXIntel_install_da.dmg>
This should not be released to the public. Aqua is not fully
ready. Also, we need to put our efforts into the 'official'
build, X11.
+1
The following Mac OS X languages are in QA: en-US, German,
Swedish, and French. French being only for the Intel platform,
and all other languages being for both the Intel and PPC
platforms.
I did some basic testing with the german build and the automated
testtesting was OK - at least the first, topten tests plus the
update tests for writer and calc.
I finished testing the Intel build for en_US today. Same errors in
b_updt.bas and c_updt.bas as I had with 2.3 and 2.3.1. It looks like
database testing will have to be looked into and FIXED for 3.0. These
are false errors and lead to unnecessary manual testing to clear them.
Is OpenOffice.org 2.4 on Mac OS X going to be released at the
same time as other platforms?
I doubt it at this point. I really don't like 'set in concrete'
release schedules. I like this: "We will not release any
software until it is fully tested and proven to be acceptable to
the common user, anything else is pure junk".
Agreed. In addition I need to confirm if the issues I found in Aqua
m4 are present in RC6, which is already the case for one of them
plus I need to figure out, why I get six leaks when starting RC6
from the comamnd line and RC6 still won't launch here using the
startscript and I still don't know why it does for nearly everybody
here except me.
It appears that something is definitely wrong with the malloc/free
cycle. I even found code that could be written better. Maybe it is
time I cracked the 'best practice' things I've learned over the last few
months and get to fixing some really poor coding practices.
It is really too late to ask use to fully test this release at
such a late hour. I would rather give the MacOSX community a
fully tested release for the official version than to have test
the program to find that we have a serious problem with a release
that is basically abandonware on its release.
I definitely will not release the en_US version until it is fully
run through.
Agree. German community will also need some more time for testing
the Mac OS X version. It's usable but we haven't done any quality
testing right now and see above my weekend was more or less
bughunting in the Aqua version and mostly easter with friends, so
that I didn't came to testing besides running the automated
testscripts.
I just finished looking at the test results and they are good. I have
approved the en_US release unless we find a serious showstopper somewhere.
James McKenzie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
