<p dir="ltr">Thierry,</p>
<p dir="ltr">Thanks!   I agree.   </p>
<p dir="ltr">Jay</p>
<div class="gmail_quote">On Sep 6, 2014 9:37 AM, "Thierry Carrez" <<a href="mailto:thierry@openstack.org">thierry@openstack.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">In that precise case, given how early it is in the freeze, I think<br>
giving a quick heads-up to the -i18n team/list should be enough :) Also<br>
/adding/ a string is not as disruptive to their work as modifying a<br>
potentially-already-translated one.<br>
<br>
Joe Cropper wrote:<br>
> +1 to what Jay said.<br>
><br>
> I’m not sure whether the string freeze applies to bugs, but the defect<br>
> that Matt mentioned (for which I authored the fix) adds a string, albeit<br>
> to fix a bug.  Hoping it’s more desirable to have an untranslated<br>
> correct message than a translated incorrect message.  :-)<br>
><br>
> - Joe<br>
> On Sep 5, 2014, at 3:41 PM, Jay Bryant <<a href="mailto:jsbryant@electronicjungle.net">jsbryant@electronicjungle.net</a><br>
> <mailto:<a href="mailto:jsbryant@electronicjungle.net">jsbryant@electronicjungle.net</a>>> wrote:<br>
><br>
>> Matt,<br>
>><br>
>> I don't think that is the right solution.<br>
>><br>
>> If the string changes I think the only problem is it won't be<br>
>> translated if it is thrown.   That is better than breaking the coding<br>
>> standard imho.<br>
>><br>
>> Jay<br>
>><br>
>> On Sep 5, 2014 3:30 PM, "Matt Riedemann" <<a href="mailto:mriedem@linux.vnet.ibm.com">mriedem@linux.vnet.ibm.com</a><br>
>> <mailto:<a href="mailto:mriedem@linux.vnet.ibm.com">mriedem@linux.vnet.ibm.com</a>>> wrote:<br>
>><br>
>><br>
>><br>
>>     On 9/5/2014 5:10 AM, Thierry Carrez wrote:<br>
>><br>
>>         Hi everyone,<br>
>><br>
>>         We just hit feature freeze[1], so please do not approve<br>
>>         changes that add<br>
>>         features or new configuration options unless those have been<br>
>>         granted a<br>
>>         feature freeze exception.<br>
>><br>
>>         This is also string freeze[2], so you should avoid changing<br>
>>         translatable<br>
>>         strings. If you have to modify a translatable string, you<br>
>>         should give a<br>
>>         heads-up to the I18N team.<br>
>><br>
>>         Finally, this is also DepFreeze[3], so you should avoid adding new<br>
>>         dependencies (bumping oslo or openstack client libraries is OK<br>
>>         until<br>
>>         RC1). If you have a new dependency to add, raise a thread on<br>
>>         openstack-dev about it.<br>
>><br>
>>         The juno-3 development milestone was tagged, it contains more<br>
>>         than 135<br>
>>         features and 760 bugfixes added since the juno-2 milestone 6<br>
>>         weeks ago<br>
>>         (not even counting the Oslo libraries in the mix). You can<br>
>>         find the full<br>
>>         list of new features and fixed bugs, as well as tarball<br>
>>         downloads, at:<br>
>><br>
>>         <a href="https://launchpad.net/__keystone/juno/juno-3" target="_blank">https://launchpad.net/__keystone/juno/juno-3</a><br>
>>         <<a href="https://launchpad.net/keystone/juno/juno-3" target="_blank">https://launchpad.net/keystone/juno/juno-3</a>><br>
>>         <a href="https://launchpad.net/glance/__juno/juno-3" target="_blank">https://launchpad.net/glance/__juno/juno-3</a><br>
>>         <<a href="https://launchpad.net/glance/juno/juno-3" target="_blank">https://launchpad.net/glance/juno/juno-3</a>><br>
>>         <a href="https://launchpad.net/nova/__juno/juno-3" target="_blank">https://launchpad.net/nova/__juno/juno-3</a><br>
>>         <<a href="https://launchpad.net/nova/juno/juno-3" target="_blank">https://launchpad.net/nova/juno/juno-3</a>><br>
>>         <a href="https://launchpad.net/horizon/__juno/juno-3" target="_blank">https://launchpad.net/horizon/__juno/juno-3</a><br>
>>         <<a href="https://launchpad.net/horizon/juno/juno-3" target="_blank">https://launchpad.net/horizon/juno/juno-3</a>><br>
>>         <a href="https://launchpad.net/neutron/__juno/juno-3" target="_blank">https://launchpad.net/neutron/__juno/juno-3</a><br>
>>         <<a href="https://launchpad.net/neutron/juno/juno-3" target="_blank">https://launchpad.net/neutron/juno/juno-3</a>><br>
>>         <a href="https://launchpad.net/cinder/__juno/juno-3" target="_blank">https://launchpad.net/cinder/__juno/juno-3</a><br>
>>         <<a href="https://launchpad.net/cinder/juno/juno-3" target="_blank">https://launchpad.net/cinder/juno/juno-3</a>><br>
>>         <a href="https://launchpad.net/__ceilometer/juno/juno-3" target="_blank">https://launchpad.net/__ceilometer/juno/juno-3</a><br>
>>         <<a href="https://launchpad.net/ceilometer/juno/juno-3" target="_blank">https://launchpad.net/ceilometer/juno/juno-3</a>><br>
>>         <a href="https://launchpad.net/heat/__juno/juno-3" target="_blank">https://launchpad.net/heat/__juno/juno-3</a><br>
>>         <<a href="https://launchpad.net/heat/juno/juno-3" target="_blank">https://launchpad.net/heat/juno/juno-3</a>><br>
>>         <a href="https://launchpad.net/trove/__juno/juno-3" target="_blank">https://launchpad.net/trove/__juno/juno-3</a><br>
>>         <<a href="https://launchpad.net/trove/juno/juno-3" target="_blank">https://launchpad.net/trove/juno/juno-3</a>><br>
>>         <a href="https://launchpad.net/sahara/__juno/juno-3" target="_blank">https://launchpad.net/sahara/__juno/juno-3</a><br>
>>         <<a href="https://launchpad.net/sahara/juno/juno-3" target="_blank">https://launchpad.net/sahara/juno/juno-3</a>><br>
>><br>
>>         Many thanks to all the PTLs and release management liaisons<br>
>>         who made us<br>
>>         reach this important milestone in the Juno development cycle.<br>
>>         Thanks in<br>
>>         particular to John Garbutt, who keeps on doing an amazing job<br>
>>         at the<br>
>>         impossible task of keeping the Nova ship straight in troubled<br>
>>         waters<br>
>>         while we head toward the Juno release port.<br>
>><br>
>>         Regards,<br>
>><br>
>>         [1] <a href="https://wiki.openstack.org/__wiki/FeatureFreeze" target="_blank">https://wiki.openstack.org/__wiki/FeatureFreeze</a><br>
>>         <<a href="https://wiki.openstack.org/wiki/FeatureFreeze" target="_blank">https://wiki.openstack.org/wiki/FeatureFreeze</a>><br>
>>         [2] <a href="https://wiki.openstack.org/__wiki/StringFreeze" target="_blank">https://wiki.openstack.org/__wiki/StringFreeze</a><br>
>>         <<a href="https://wiki.openstack.org/wiki/StringFreeze" target="_blank">https://wiki.openstack.org/wiki/StringFreeze</a>><br>
>>         [3] <a href="https://wiki.openstack.org/__wiki/DepFreeze" target="_blank">https://wiki.openstack.org/__wiki/DepFreeze</a><br>
>>         <<a href="https://wiki.openstack.org/wiki/DepFreeze" target="_blank">https://wiki.openstack.org/wiki/DepFreeze</a>><br>
>><br>
>><br>
>>     I should probably know this, but at least I'm asking first. :)<br>
>><br>
>>     Here is an example of a new translatable user-facing error message<br>
>>     [1].<br>
>><br>
>>     From the StringFreeze wiki, I'm not sure if this is small or large.<br>
>><br>
>>     Would a compromise to get this in be to drop the _() so it's just<br>
>>     a string and not a message?<br>
>><br>
>>     Maybe I should just shut-up and email the openstack-i18n mailing<br>
>>     list [2].<br>
>><br>
>>     [1] <a href="https://review.openstack.org/#__/c/118535/" target="_blank">https://review.openstack.org/#__/c/118535/</a><br>
>>     <<a href="https://review.openstack.org/#/c/118535/" target="_blank">https://review.openstack.org/#/c/118535/</a>><br>
>>     [2]<br>
>>     <a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-i18n" target="_blank">http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-i18n</a><br>
>>     <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a>><br>
>><br>
>>     --<br>
>><br>
>>     Thanks,<br>
>><br>
>>     Matt Riedemann<br>
>><br>
>><br>
>>     _________________________________________________<br>
>>     OpenStack-dev mailing list<br>
>>     OpenStack-dev@lists.openstack.__org<br>
>>     <mailto:<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>><br>
>>     <a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev" target="_blank">http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev</a><br>
>>     <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>><br>
>><br>
>> _______________________________________________<br>
>> OpenStack-dev mailing list<br>
>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>> <mailto:<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
<br>
--<br>
Thierry Carrez (ttx)<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>