Re: [openstack-dev] [nova] [all] Updated String Freeze Guidelines

2015-09-14 Thread John Garbutt 
On 10 September 2015 at 20:37, Thierry Carrez  wrote:
> John Garbutt wrote:
>> [...]
>> 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?
>
> That sounds pretty good.

As promised, I have attempted to add this into the project-team-guide,
to help avoid any wiki related issues in the future:
https://review.openstack.org/223011

Thanks,
John

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] [all] Updated String Freeze Guidelines

2015-09-10 Thread Thierry Carrez 
John Garbutt wrote:
> [...]
> 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?

That sounds pretty good.


-- 
Thierry Carrez (ttx)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] [all] Updated String Freeze Guidelines

2015-09-09 Thread John Garbutt 
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev