hmm, I think the policy should depends on projects.
For projects which don't have active translations, I think it's OK to
backport.
For projects which have active translations, "Exception procedure" of
StringFreeze could help.
Translators need to be notified for the changes.

If you don't know whether the project has active translations or not,
"Exception procedure" can help, anyway.

Best regards
Ying Chun Guo (Daisy)


Matt Riedemann <mrie...@linux.vnet.ibm.com> wrote on 2016/02/18 08:16:26:

> From: Matt Riedemann <mrie...@linux.vnet.ibm.com>
> To: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev@lists.openstack.org>, openstack-i...@lists.openstack.org
> Date: 2016/02/18 08:18
> Subject: [Openstack-i18n] [stable][i18n] What is the backport policy
> on i18n changes?
>
> I don't think we have an official policy for stable backports with
> respect to translatable string changes.
>
> I'm looking at a release request for ironic-inspector on stable/liberty
> [1] and one of the changes in that has translatable string changes to
> user-facing error messages [2].
>
> mrunge brought up this issue in the stable team meeting this week also
> since Horizon has to be extra careful about backporting changes with
> translatable string changes.
>
> I think on the server side, if they are changes that just go in the
> logs, it's not a huge issue. But for user facing changes, should we
> treat those like StringFreeze [3]? Or only if the stable branches for
> the given project aren't getting translation updates? I know the server
> projects (at least nova) is still get translation updates on
> stable/liberty so if we do backport changes with translatable string
> updates, they aren't getting updated in stable. I don't see anything
> like that happening for ironic-inspector on stable/liberty though.
>
> Thoughts?
>
> [1] https://review.openstack.org/#/c/279515/
> [2] https://review.openstack.org/#/c/279071/1/ironic_inspector/process.py
> [3] https://wiki.openstack.org/wiki/StringFreeze
>
> --
>
> Thanks,
>
> Matt Riedemann
>
>
> _______________________________________________
> Openstack-i18n mailing list
> openstack-i...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>
__________________________________________________________________________
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

Reply via email to