Open Stack

Sorry late post.

This mail hits me a question how the upstream projects should handle
translation bugs for stable branches which the translation platform
(zanata) no longer supports.
Should the upstream projects accept translation fixes which are
directly proposed to git repositories, or can they reject them as the
translation should happen in translate.openstack.org (though there is
no way to fix translation actually)?

Akihiro

On Wed, May 8, 2019 at 10:58 PM Ian Y. Choi <ianyrchoi at gmail.com> wrote:
>
> Hello team,
>
>
> Just I would like to share with team members that I18n team will stop
> translation for Queens stable version
>
> due to no translation activities, low demand, and low bandwidth on such
> a stable branch.
>
>
> I wanna more share that:
>
> - If some translators find bugs on latest two releases (Stein, Rocky),
> please share via this mailing list or Launchpad.
>
> - Such decision will start after [1] is merged.
>
> - Still other bug fixes would be fine for extended maintence purpose
> [2]. If someone finds significant translation bugs on such old versions,
>
> please share via this mailing list so that we can discuss how to deal with.
>
>
>
> With many thanks,
>
>
> /Ian
>
>
> [1] https://review.opendev.org/#/c/656047/
>
> [2]
> https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html
>
>
> _______________________________________________
> OpenStack-I18n mailing list
> OpenStack-I18n at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n