<html><body>
<p><font size="2" face="sans-serif">Hello, Julie</font><br>
<br>
<font size="2" face="sans-serif">Thank you for bring it up.</font><br>
<font size="2" face="sans-serif">Yes, the wiki page for string freeze should be updated.</font><br>
<br>
<tt><font size="2">See my comments below.</font></tt><br>
<br>
<font size="2" face="sans-serif">Best regards<br>
Ying Chun Guo (Daisy)<br>
</font><br>
<br>
<tt><font size="2">Julie Pichon <jpichon@redhat.com> wrote on 2014/03/26 02:43:00:<br>
<br>
> Julie Pichon <jpichon@redhat.com> </font></tt><br>
<tt><font size="2">> 2014/03/26 02:43</font></tt><br>
<tt><font size="2">> <br>
> To</font></tt><br>
<tt><font size="2">> <br>
> "openstack-i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org>, </font></tt><br>
<tt><font size="2">> <br>
> cc</font></tt><br>
<tt><font size="2">> <br>
> Subject</font></tt><br>
<tt><font size="2">> <br>
> [Openstack-i18n] Clarifying String Freeze</font></tt><br>
<tt><font size="2">> <br>
> Hi all,<br>
> <br>
> During the weekly Horizon meeting [0], a few questions from the Horizon<br>
> team came up about String Freeze. I think the wiki page on String Freeze<br>
> [1] at the moment does not match the wishes of the translation team,<br>
> based on previous conversations [2].<br>
> <br>
> It would be really helpful if the wiki page could be updated to match<br>
> what the i18n team would prefer. At the moment, in Horizon it seems<br>
> what we're doing, and planning on doing, is this (somewhat similar to<br>
> what happened in Havana):<br>
> <br>
> - During String Freeze and until RC1, small string changes are ok<br>
> (Horizon core can just approve)</font></tt><br>
<tt><font size="2">> - During String Freeze, string changes in the "grey zone" should use<br>
> the exception approval process on the wiki (email to i18n list)</font></tt><br>
<br>
<tt><font size="2">What do you mean by "grey zone"?</font></tt><br>
<tt><font size="2">Does it include the "small string changes" mentioned in the previous item? </font></tt><br>
<tt><font size="2"><br>
> - After RC1 is released, every string change should follow the<br>
> exception approval process on the wiki (email to i18n list) ??? -<br>
> this isn't clearly defined yet, maybe it needs to be earlier?<br>
> </font></tt><br>
<br>
<tt><font size="2">I think, after RC1, we should avoid string changes. </font></tt><br>
<tt><font size="2">If a string change is required strongly, I18n team should be notified.</font></tt><br>
<tt><font size="2">Because most of translation teams will complete translation before RC1 is shipped.</font></tt><br>
<tt><font size="2">Then they might not pay much attention to the update of strings.</font></tt><br>
<tt><font size="2">I think the third item in the process of "exception of SF" has mentioned to send email to openstack-i18n.</font></tt><br>
<tt><font size="2"><br>
> Point #3 is about when the "soft freeze" needs to become a "hard freeze".<br>
> <br>
> What is the grey zone? I'm not entirely sure either. An example was:<br>
> adding several new strings for what could be considered a<br>
> "mini-feature", during the RC period. Perhaps we can start with this<br>
> kind of examples + "when in doubt, ask on the i18n list" to define what<br>
> is the grey zone.</font></tt><br>
<br>
<tt><font size="2">It's hard to define the "grey zone".</font></tt><br>
<tt><font size="2">In my mind, below two cases should be accepted:</font></tt><br>
<tt><font size="2">1. A string is misunderstanding and should be updated.</font></tt><br>
<tt><font size="2">2. A string should be translated yet not marked with _().</font></tt><br>
<br>
<tt><font size="2">What else is in your mind?</font></tt><br>
<br>
<tt><font size="2">> <br>
> In general, I think updating the wiki page would really help reviewers<br>
> assess patches with a clearer understanding of what is helpful to the<br>
> i18n/translation team during string freeze, and what might require<br>
> exception approval or more discussion.<br>
> <br>
> Thank you,<br>
> </font></tt><br>
<br>
<tt><font size="2">I think, a notification </font></tt><tt><font size="2">mechanism </font></tt><tt><font size="2">will be helpful.</font></tt><br>
<tt><font size="2">We might not force developers to add "String Impact" tag.</font></tt><br>
<tt><font size="2">We could revise the jobs to update Transifex resources </font></tt><br>
<tt><font size="2">to add a step to send a notification to translators.</font></tt><br>
<tt><font size="2">It's possible.</font></tt><br>
<tt><font size="2"><br>
> Julie<br>
> <br>
> [0]<br>
> <a href="http://eavesdrop.openstack.org/meetings/horizon/2014/horizon">http://eavesdrop.openstack.org/meetings/horizon/2014/horizon</a>.<br>
> 2014-03-25-16.00.log.html<br>
> [1] <a href="https://wiki.openstack.org/wiki/StringFreeze">https://wiki.openstack.org/wiki/StringFreeze</a><br>
> [2]<br>
> <a href="http://lists.openstack.org/pipermail/openstack-dev/2014-March/029868.html">http://lists.openstack.org/pipermail/openstack-dev/2014-March/029868.html</a><br>
> <br>
> _______________________________________________<br>
> Openstack-i18n mailing list<br>
> Openstack-i18n@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>
> <br>
</font></tt></body></html>