Hi Andre,
André Schnabel schrieb:
Hi,
reading todays release meeting log, I found that several l10n related
Issues have been sugested but rejected as stoppers for 3.0 beta.
The numbers are: 88441, 88444, 88325, 88387, 88461, 88465, 88469, 88471,
88478
All those issues are merge problems - means, the translation is ok and
has been verified in cws localisation28 but has not been integrated into
the master.
I consider these issues as stopper for two reasons:
- Beta testers will fokus on new features - and actually (some of) the
new features are affected by those issues. We will receive false error
reports on that
- there is a lager localization test round scheduled, that would be
based on regular beta builds - mainly to test the correct localization
of the new features (with the larger community). If we already know,
that localization of new features is broken, we will loose many testers
(it is nonsens to test something, if you already know it is broken)
André
Of course we don't want to generate too much unnecessary work by a
multitude of duplicate error reports for already known issues. OTOH
there is always an amount of issues which we don't regard as blockers
for a release where we have to accept that users will encounter the
issue and file a new issue.
So IMHO we just have to verify the above issues like all the other
issues we know for this release, and have to see whether they are really
showstoppers. And during the Release Meeting the above l10n issues were
_not_ regarded as blockers.
OTOH it's not that we are idle and don't want to fix the bugs. Ivo is
currently creating a new CWS l10nfixooo3b for showstopper fixes for the
Beta. He will try to at least fix the issues which are easily and safely
fixable. But some of the above issues (and I just saw that Ivo gave some
more details on them in another mail) are hard to fix and some even
require a new translation cycle. And I am not sure whether we really
want to accept the delay of several weeks which would be required for
this new translation handover, translation, integration into the code etc.
Therefore I'd vote for proceeding with the OOo 3.0 Beta as planned
despite of the above l10n issues.
Regards,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
