String Freeze Guidelines Update
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
On 09/09/15 19:38, John Garbutt wrote:
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.
Just as an extra data point, String Freeze might change for the M cycle. Due to switching to Zanata[1] for translations, which is hopefully well in hand for the Liberty cycle, with some extra work we should be able to translate stable versions. My current plan is to discuss that with -infra and the translators themselves at the Tokyo Summit. 1: http://specs.openstack.org/openstack-infra/infra-specs/specs/migrate_to_zana... Cheers, -- Steve "...In the UNIX world, people tend to interpret `non-technical user' as meaning someone who's only ever written one device driver." - Daniel Pead
On 9 September 2015 at 12:45, Steve Kowalik <steven@wedontsleep.org> wrote:
On 09/09/15 19:38, John Garbutt wrote:
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.
Just as an extra data point, String Freeze might change for the M cycle. Due to switching to Zanata[1] for translations, which is hopefully well in hand for the Liberty cycle, with some extra work we should be able to translate stable versions. My current plan is to discuss that with -infra and the translators themselves at the Tokyo Summit.
1: http://specs.openstack.org/openstack-infra/infra-specs/specs/migrate_to_zana...
OK, no problems. Let us know how we can help when that changes. Thanks, John
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. Thanks, Akihiro 2015-09-09 18:38 GMT+09:00 John Garbutt <john@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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 9 September 2015 at 15:12, Akihiro Motoki <amotoki@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@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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
participants (3)
-
Akihiro Motoki
-
John Garbutt
-
Steve Kowalik