Bonjour,

welcome to the QA project. It's great to see someone willing to do release QA for MacOSXPPC builds.

Here's the most current 3.1.1 PPC release candidate:
http://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/3.1.1rc2_20090827/OOo_3.1.1rc2_20090827_MacOSXPowerPC_install.dmg

or this one from the good-day mirror Unlogisch.ch (hosted by Rafael Bircher):
http://mirror.unlogisch.ch/ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/3.1.1rc2_20090827/OOo_3.1.1rc2_20090827_MacOSXPowerPC_install.dmg

MD5 (OOo_3.1.1rc2_20090827_MacOSXPowerPC_install.dmg) = 1d9182a0bda334c8e4b0bf15b9dbc9ff

First you'll need an OpenOffice.org account:

http://www.openoffice.org/servlets/Join

Then please register within the QA project http://qa.openoffice.org/servlets/ProjectMembershipRequest and join the QA mailing list [email protected]

To be able to change the status of the IssueTracker issue that you send as distribution request http://www.openoffice.org/issues/enter_bug.cgi?component=qa you should send me your OpenOffice.org login name. Without this ID I'm not able to change appropriate "Canconfirm" role within IssueTracker's database. I also need this to create an account at http://qatrack.services.openoffice.org for you to allow you to add this build to the releases tracking tool QATrack.

I believe here are several QA members who will help you to create a running VCL TestTool test environment. Maybe Rafael Bircher would like to help. AFAIK he's also running a PPC environment. CC'ed him.


Gallomimia schrieb:
Hi gang. I'd like to become involved in quality assurance for Open
Office MacPPC platform. I have a Mac G4 running 10.5.8 and I'd very
much like to see the 3.1.1 RC approved for distribution. English
language only unfortunately.

I would appreciate some directions on how to proceed, what to
download, where to sign up, and what reports to generate.

Kind regards, Joost

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to