On 9/9/2015 4:59 AM, John Garbutt wrote:

Hi,

I have had quite a few comments from folks about the string freeze being too strict.

It was noted that: * users will prefer an untranslated log, over a silent failure * translators don't want existing strings changing while they are translating them * translators tooling can cope OK with moved strings and new strings

After yesterday's cross project meeting, and hanging out in #openstack-i18n I have come up with these updates to the String Freeze Guidelines: https://wiki.openstack.org/wiki/StringFreeze

Basically, we have a Soft String Freeze from Feature Freeze until RC1: * Translators work through all existing strings during this time * So avoid changing existing translatable strings * Additional strings are generally OK

Then post RC1, we have a Hard String Freeze: * No new strings, and no string changes * Exceptions need discussion

Then at least 10 working days after RC1: * we need a new RC candidate to include any updated strings

Is everyone happy with these changes?

Thanks, John

_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

Sounds OK. I'm using https://review.openstack.org/#/c/203809/ as a test - it introduces a new exception which means new translations of that exception message. -- Thanks, Matt Riedemann