Hi Thorsten,
Thorsten Ziehm ha scritto:
Hi Andre,
André Schnabel wrote:
Hi,
Pavel Janík schrieb:
that were correct on the CWS and which are now not correct on the
master. The other issues can be found on the CWS as well as on the
master. Therefore I don't see some general kind of processing
problem we have to fix.
I see one. The probblem is that we do not merge strings often, thus
l10n testers do not have a chance to test their translations soon.
This esp. applies to Sun languages :-( And as there are *many* l10n
testers using Sun languages...
Yes - we actually had just two days to test the CWS builds (builds
have been available on 15th, afternoon, last CWS integration for Beta
was 17th).
This is an extremely short time, esp. if there is no time to fix
anything in the CWS. But we found problems in the CWS builds !
As I think Pavel talked about more translation cycles. This is a good
idea, but in the past it doesn't fit with the integration with our new
features and their online help. The QA got mostly always all features
in the week before Feature Freeze and nearly all of them are integrated
in 1-2 weeks. The result is, that the L10N communities will get more
cycles but only in one you got nearly the same mass as now.
So we have to work on regular integration of UI features, I think.
The CWS was integrated anyway .. and we again had just two days
before release status meeting. We found new issues but again have no
chance to get these fixed before Beta goes out.
Yes, the time frame was very short for the L10N teams. But as wrote
above, it's the same problem. The features came in late in QA and
the result is that the translation cycle starts often with a delay.
As I do try to schedule dealines for translation handover and delivery
deadlines, maybe QA should also start scheduling QA handover dates?
Based on the release schedule QA should know wich is the latest date to
accept features, right? If features come in late then they can be
accepted but the release map needs to be readjusted so that translation
and l10n testing can still be performed.
Maybe one of the release engineers who don't see those l10n issues as
stopper would like to volunteer to coordinate l10n testing under such
circumstances?
What do you need, an Wiki page with the known translation issues?
Since it's all in IssueTracker, I don't see the need to set up a wiki
which needs to be manually updated...
Just my 2 cents,
Rafaella
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
