Hello, Akihiro,

I understand the situation.
I have different choice to solve this issue.

I think, we can rename the current resources, by adding a prefix "icehouse".
Then we don't need help from Infra team.
You or I can do it immediately just after the master branch is opened to Juno.
The only disadvantage is that this solution will confuse some of our translators.
I can send the new links to ML and remind people we have switched versions.

Horizon is the only project for Icehouse.
If we expend the scope to include more projects in the future releases,
we don't need to bother Infra team to stop several sync jobs.

How do you think?
I'd like to hear others thoughts too.

Best regards
Ying Chun Guo (Daisy)


Akihiro Motoki <amotoki@gmail.com> wrote on 2014/03/25 22:33:14:

> Akihiro Motoki <amotoki@gmail.com>
> 2014/03/25 22:33
>
> To
>
> "openstack-i18n@lists.openstack.org" <Openstack-i18n@lists.openstack.org>,
>
> cc
>
> Subject
>
> [Openstack-i18n] Horizon upstream_translation_update Jenkins job
>
> Hi Daisy,
>
> Perhaps RC1 may be shipped this week and the master branch
> will be opened to Juno development.
> Even after the master branch is opened to Juno,
> Transifex resources are still targeted to Icehouse translations.
> We need to disable upstream_translation_update for Horizon temporarily.
> Otherwise Transifex resources will be synced with Juno code.
> Could you coordinate it with the infra team?
>
> At now Horizon is the only project whose translation work
> is being done synced with the release cycle and
> we tend to encounter the first thing :-(
>
> Thanks,
> Akihiro
>
> _______________________________________________
> Openstack-i18n mailing list
> Openstack-i18n@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>