[OpenStack-I18n] Stop translating non-UI projects for stable branches?
Ian Y. Choi
ianyrchoi at gmail.com
Sun Apr 26 17:56:45 UTC 2020
Let's discuss after Ussuri release. Agree with reflecting the current
translator nature today.
Related thoughts and discussions might be:
- List of UI projects: how we get this information?
- Target release: only for cycle-with-rc or including
cycle-with-intermediary
- I18n team needs to stay with deeper eyes on release model changes
(e.g., Horizon's cycle-with-rc -> cycle-with-intermediary during Ussuri
cycle) & translation effort (e.g., how many translations are going on
many projects)
- Needs to think about procedure how to deal with translation bugs on
stable branches for master-only projects
With many thanks,
/Ian
On 4/26/2020 9:31 PM, Andreas Jaeger wrote:
> Looking at the work to branch a new release and the amount of
> translation done on stable branches for the non-ui projects (ceilometer,
> cinder, nova etc), I propose to translate them *only* on master.
>
> So, we would continue to translate on master and stable horizon and
> friends - and that's all.
>
> If there's a specific project that needs translation, we can change that
> one for sure.
>
> This reflects IMHO how translators translate today.
>
> I've proposed the following change and marked it WIP for discussion here
> and waiting until Ussuri release:
> https://review.opendev.org/723217
>
> Andreas
More information about the OpenStack-I18n
mailing list