Guido Ostkamp, 19-01-2007 17:40:
Hello Caio Tiago,
Yesterday I filed
<http://www.openoffice.org/issues/show_bug.cgi?id=73643> (Issue
#73643) after checking it did not work in OOF680_m1.
Now "fst" has closed the issue and called it a duplicate of
<http://www.openoffice.org/issues/show_bug.cgi?id=72502> (Issue 72502).
But Issue 72502 should have been already fixed around Dec. 20th last
year and has set target milestone OOo 2.2, so I think the fix should
have been already included in OOF680_m1, but it still doesn't work.
Can you please clarify?
The issue was not "closed".
You misunderstood me. I did not say #72502 was closed, but my issue
#73643 was closed after setting it duplicate.
No, I didn't. I meant issue #72502 was not closed, so you shouldn't
assume it had been integrated to the master and file another issue for
the same issue.
Verified means verified on the CWS (branch) the developer is working on.
Yes, that's clear to me. However I did expect that OOF680_m1, after
calling it officially a "beta" is complete though it is not an "RC" yet.
What do you mean with "complete"?
It won't add new features neither change the UI (both already are froozen).
The wiki page for the 2.2 release:
<http://wiki.services.openoffice.org/wiki/OOoRelease22>
tells the code freeze is expected to January 25th, 2007.
These are just minor bugfixes, off course it would be better to have it
integrated in OOF680_m1.
The issue was fixed there, but that CWS was not integrated to OOF680_m1.
This clarifies things a bit. I consider this bug a release critical issue.
Can we expect that this CWS will be integrated before release of 2.2?
In the next milestone.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
