"Team activities with release" are described in https://docs.openstack.org/i18n/latest/release_management.html , but let me first try to clarify more on I18n team activites with stable versions in Zanata regarding project release activities. Generally, there are two main reasons creating and maintaining stable versions in Zanata: 1. Hard StringFreezes with RC1, RC2, and so on  : checking translation is much better using stable versions(with translation checksite, ideally)  : That's why creating stable versions in Zanata is encouraged when there is first stable-xx branch in project repositories 2. Maintaining translation bugs on stable branches  : There might be translation bugs on released artifacts - tranlation bugs can be fixed by editing stable versions in Zanata, syncing with project repos, and releasing new artifacts on target stable branches.  : Usually, after final real stable artifacts are announced, then translations on stable versions from the first part are merged into master version for the next release. For the first part, Ideally, it would be excellent if there are enough translation demand, stable version creation activities in Zanata, translation activites on stable versions, communications via I18n-release cross project liaison, and review activities through translation checksite, and those are interactive together. If not, then I think I18n team needs to minimize the targets for such purpose or think differently how I18n team reacts with final new stable version creation. For the second part, the glad news I wanna share is that now all stable versions in Zanata now have content. More details are described in below: - Now projects mentioned in http://lists.openstack.org/pipermail/openstack-i18n/2019-March/003382.html should have "stable-stein" versions in Zanata   : except "sahara-plugin-*" since there is no translated resource even on master version -> I wanna set that those will be synced only for master repos. - Some stable document versions including "keystone, octavia-dashboard, trove, watcher" projects were already filled translations from master (thanks a lot, Andreas and/or Frank!),   but a few of them still had releasenotes documents, which need to be deleted on stable versions: "murano-dashboard, solum-dashboard, swift, trove-dashboard, zaqar, zaqar-ui, zun-ui". - One zh-CN translator did translations from empty content stable-stein version for ironic-ui project. Since the content were actually the same as master branch,   I deleted stable-stein version on ironic-ui project, re-created stable-version by copying from master version, and removed releasenotes document on stable-stein version. - Strangely, there are no releasenotes document on master version for karbor-dashboard and neutron-lbaas-dashboard projects - need to be investigated further. As Train PTL, I will identify how much translations were for Stein release and try to find better ways how I18n team can work well regarding new release activites which will happen after around 6 months. With many thanks, /Ian Akihiro Motoki wrote on 4/5/2019 1:35 AM:

I see no content for stable-stein version for example in neutron-fwaas-dashboard [1]. What should we do? I am really confused with the process around stable-stein cut....

[1] https://translate.openstack.org/project/view/neutron-fwaas-dashboard?dswid=1...

On Mon, Apr 1, 2019 at 7:21 PM Frank Kloeker <eumel@arcor.de <mailto:eumel@arcor.de>> wrote:

Good morning,

last week I was on a business trip and just wondering about ML activities. But for sure, we have release weeks and thanks for raising up that topic. Based on Ian's work I just cleaned up the Stein Dashboard with stable branches as available [1]. So it's more clear what translators have to do, I mean translate stable branch instead of master. There is no clear handover between project teams when a stable branch is available, so this needs to investigate by Zanata admin/PTL, or the failed job list on [2]. A lot of good jobs are already running on [3] Further I investigted Ian's creation of empty versions in Zanata and I would say that won't work well, because that are post jobs and not periodic jobs in Zuul. So if now merge on stable branch will happen, the po files won't sync to Zanata. Or it will take days, like in [4]. On the other hand, someone will translate things targeting in that release, then it's required to copy the stable version from master as usually. I know, this takes some time and work, but at the moment there is no improvement because Zanata developement is already gone and the feature set on API is at it is.

Regarding the second question for Horizon on translation check site it might be a question for the Horizon team. From my experience with language settings it depends mostly on your browser settings. So I'm not sure if it's really a bug.

kind regards

Frank

[1] https://translate.openstack.org/version-group/view/Stein-dashboard-translati... [2] http://zuul.openstack.org/builds?job_name=upstream-translation-update&job_name=propose-translation-update&result=Failure [3] http://zuul.openstack.org/builds?job_name=upstream-translation-update&branch=stable%2Fstein [4] http://zuul.openstack.org/builds?job_name=upstream-translation-update&project=openstack%2Fdesignate-dashboard

Am 2019-03-27 03:21, schrieb Yuko Katabami: > Hi Frank and all, > > I have a couple of questions about Horizon UI translation. > Hope you can help me. > > 1. Is stable-stein version going to be created soon in Zanata? I > noticed that the projects in github already have the new branch. > > 2. With Octavia Dashboard, I am not able to see Japanese translations > in Horizon even though it is 100% completed in master. I can see that > po files are imported properly: > https://github.com/openstack/octavia-dashboard/tree/master/octavia_dashboard... > Is there anything I need to do to be able to see it in my environment? > > Many thanks in advance. > > Yuko > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n@lists.openstack.org <mailto:OpenStack-I18n@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org <mailto:OpenStack-I18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n