Re: 2.4 stringset freeze

Hi Hub,

Hubert Figuiere wrote:
>
> Tomas Frydrych wrote:
>
>> I suggest that we freeze strings for 2.4 on May 20th, and do an
>> announcement asking for translations to be updated. Therefore, would
>> everyone go through the bugs they are expecting to fix for 2.4 to see
>> if any of them will require new strings (ensuring the strings will be
>> in place by the freeze date, of course).
>>
>> I have opened meta bug 8916 to conveniently gather these, so that if
>> anyone comes across a bug that obviously falls into that category,
>> please add it as a dependency to 8916 (even if you are not the person
>> who would be fixing it).
>>
>
> It is a little bit early to string freeze, isn't it ?
>
> 2.3.99 would be a better time IMHO

We have been in feature freeze for 3 weeks now, so there should not be
any major changes to the UI -- if you know about a serious UI problem on
any platform then please open a bug report and add dependency to 8916,
and preferebly deal with the problem now. (It is quite easy to judge
from bug reports whether a bug needs a string change or not, and there
are another two weeks till the proposed deadline to identify these and
deal with them.)

The point is that we need to give the translators time to update the
string set, and we cannot expect them to be updating them 20 times from
now till the release. The public beta is way too late, we want the beta
to be localised as much as possible.

If it happens that one or two strings absolutely have to be changed
after the deadline, we will, of course, do so. The proposed date of May
20th means the translators will get 4 weeks to do their job, which is
not excessive, but I think reasonable. I would rather have the UI 99%
correct in all the UI languages that we support than have it 100% in one
or two because there just was not enough time for the translators -- we
gain nothing by pushing the string freeze back.

Tomas
Received on Mon May 9 22:50:28 2005