On 13/03/14 09:28, Akihiro Motoki wrote: > +1 > > In my understanding "String Freeze" is a SOFT freeze as Daisy describes. > Applying string freeze to incorrect or incomprehensible messages is > not good from UX point of view > and shipping the release with such strings will make the situation > worse and people feel OpenStack is not mature > and can misunderstand OpenStack doesn't care for such detail :-( > > From my experience of working as a translator and bridging Horizon and > I18N community > in the previous releases, the proposed policy sounds good and it can > be accepted by translators.
That sounds good to me as well. I think we should modify the StringFreeze page [1] to reflect this, as it sounds a lot more strict than what the translation team actually wishes for. Thanks, Julie [1] https://wiki.openstack.org/wiki/StringFreeze > Thanks, > Akihiro > > > On Thu, Mar 13, 2014 at 5:41 PM, Ying Chun Guo <guoyi...@cn.ibm.com> wrote: >> Hello, all >> >> Our translators start translation and I18n compliance test since string >> frozen date. >> During the translation and test, we may report bugs. >> Some bugs are incorrect and incomprehensible messages. >> Some bugs are user facing messages but not marked with _(). >> All of these bugs might introduce string changes and add new strings to be >> translated. >> I noticed some patches to fix these bugs got -1 because of "string freeze". >> For example, https://review.openstack.org/#/c/79679/ >> and https://review.openstack.org/#/c/79948/ >> >> StringFreeze -> Start translation & test -> Report bugs which may cause >> string changes -> Cannot fix these bugs because of StringFreeze. >> So I'd like to bring this question to dev: when shall we fix these errors >> then? >> >> From my point of view, FeatureFreeze means "not accept new features", and >> doesn't mean "cannot fix bugs in features". >> StringFreeze should mean "not to add new strings". But we could be able to >> improve strings and fix bugs. >> I think shipping with incorrect messages is worse than strict string freeze. >> >> From my experiences in Havana release, since StringFreeze, there are >> volunteers from Horizon team who would >> keep an eye on strings changes. If string changes happen, they would send >> email >> to I18n ML to inform these changes. Many thanks to their work. >> In Havana release, we kept on those kind of bug reporting and fixing till >> RC2. >> Most of them are happened before RC1. >> >> Now I hope to hear your input to this situation: when and how should we fix >> these kind of bugs in Icehouse? >> >> Best regards >> Ying Chun Guo (Daisy) >> >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
