[Openstack-i18n] Thought on String Freeze

Akihiro Motoki amotoki at gmail.com
Wed Jun 3 15:25:47 UTC 2015


Hi I18N folks,

# Congratulation for the official I18N project!!

I first thought to send this mail to the dev list, but it seems better
to share my thought in the I18N folks first.

Problems
==========

I am feeling that String Freeze does not work well in the past several
releases.There are several
I think we should not apply String Freeze for projects for which not so
many translators work on.

As far as I understand, Horizon and documentations are targets
for most translations in the past several releases.
On the other hands, core reviewers of projects other than Horizon and docs
(including keystone) were taking care of String Freeze exception WELL.

My Proposal
=============

Considering the current status, I think we should limit "String Freeze"
only to projects which translators are interested in.
My idea is to declare projects we would like to enable "String Freeze"
just after Liberty-3 is cut.
By doing so, other projects no longer need to take care of String Freeze
exception.

(Note that the freeze date of the documentation projects are different and
we can apply some different policy on documentations).

Thought?
I cannot join the team meeting tomorrow due to LinuxCon/CloudOpen Japan,
but I hope you will share your thought on this topic.

Thanks,
Akihiro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-i18n/attachments/20150604/6e560ac2/attachment.html>


More information about the Openstack-i18n mailing list