Jim Allan wrote:
Check the issue at http://qa.openoffice.org/issues/show_bug.cgi?id=79121
which was supposed to be fixed with a patch to be applied on OpenOffice
3.0 and was supposedly a duplicate of the issue at
http://qa.openoffice.org/issues/show_bug.cgi?id=66693 .
But it is still not fixed in OpenOffice 3.0 Beta despite being retired
from the listing. So I resubmitted the issue at
http://qa.openoffice.org/issues/show_bug.cgi?id=90129 . So far as I can
see no-one has even looked at it.
Yeah, well the Issue tracker only gives you part of the story - it may
be marked fixed...but if you really want to know if it is about to
become 'available', you have to look into the other system EIS...doing
that just now:
The system shows that the code checked in for the fix passed the build /
test cycle for Windows with 0 problems.
The test runs on Linux / Mac are both showing open problems - remember
these are not the same problem as the actual application level issue,
rather problems building for the target OS.
Anyway - right now it gets even harder to follow sometimes because there
are two 3.0 code lines that have not merged yet. "BEA3.0 Beta m_x" and
"DEV300 m_xx".
In the case of this issue the integration appears to have happened just
after the build of BEA3.0 Beta m_2, the latest version still available
for download via the main website. m_3 is getting real close I think.
It shows that it is now included with the DEV300 m_11 developer build
and later. In other words if you go to the web site and download the
Beta release, you will not find the fix, if instead you download the
developer snapshot, currently at DEV300 m_17 you should. At least that
is what the public records seem to indicate.
For the others, all I can do is commiserate...and I do.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
