Open Stack

On 9 September 2015 at 15:12, Akihiro Motoki <amotoki at gmail.com> wrote:
> Thanks John for improving the guidelines.
>
> The new guideline almost makes sense to me.
> The concept of "Soft string freeze" and "Hard string freeze" is really
> reasonable,
> and it is exactly what Horizon team has done.
>
> I have one note on "Soft string freeze" as a previous Horizon I18N liaison
> is
> that fixes on typos or issues related to translations need to be fixed
> promptly
> in the period of "Soft string freeze". In my past experience, translators
> tend
> to find string mistakes or translation issues (for example, hard to
> translate
> concatenated strings in some languages due to word order).
> I believe it is worth considered and mentioned in the wiki.

Ah, yes. Thats a good idea, I will add something to mention that.

Thanks,
John

>
> 2015-09-09 18:38 GMT+09:00 John Garbutt <john at johngarbutt.com>:
>>
>> Hi all,
>>
>> Daisy and I have been chatting about the String Freeze guidelines.
>>
>> After our conversations, and some discussion in the cross project
>> meeting, I have updated them here:
>> https://wiki.openstack.org/wiki/StringFreeze
>>
>> It seems the general string freeze got accidentally got made super strict.
>>
>> Hopefully this slight relaxing of the rules will work better for
>> everyone, particularly for our users.
>>
>> Certainly right now we are only merging bug fixes, but they often
>> include the need for extra log messages, or similar. Right now we are
>> hiding logs as debug messages, etc, to try and get them merged during
>> the freeze. The above changes should stop all that pain, and help our
>> users too.
>>
>> Does this sound sensible?
>>
>> Thanks,
>> John
>>
>> IRC: johnthetubaguy
>>
>> _______________________________________________
>> Openstack-i18n mailing list
>> Openstack-i18n at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>
>