From this point of view, there is no reason to give -1/-2 to the
Hi, I think we need to consider two things: (a) maintenance policy of stable release translations (b) how to automate the process Regarding (a), in my understanding, we already have a consensus to maintain translation up-to-date though it is not well-documented so far. Daisy renamed Transifex horizon resources to *-havana to allow this. proposed patch from Julie. Regarding (b), we should move to the automated process as Daisy wrote and I wrote about it several times :-) We need a volunteer to work on it. This is just a topic of the process.
I think, it's no question for Horizon to use #1 to update Transifex resources automatically.
Agree in general. Before automating the process, we need to discuss how to deal with the switch from master to milestone-proposed just before the release. Once RC1 is shipped, master branch is open to development of the next release but translations teams still want to work on the release.
How about #2 ? I remember originally Horizon team disabled automatics downloading because messy characters in po.en would cause broken in Horizon test. Now this issue has been resolved.
Yes. It was really an old topic and fixed. It was because English PO file has Georgian characters and the unit tests failed. Horizon no longer has English PO files since it is the source language and the problem never happens now.
So I wonder if Horizon would like to adopt #2 to enable the automatics translation downloading now.
For master branch, the automated translation imports works to me. How about stable branch and milestone-proposed? For stable branch, we need to import well-reviewed translations. How can we achieve this with an automated process? I think this is the reason that automated process of translation imports is not enabled by default now. For milestone-proposed, the meaning of the branch changes depending on the phase, I think it is not easy to make the process automated. Thanks, Akihiro On Mon, Jan 13, 2014 at 11:34 AM, Ying Chun Guo <guoyingc@cn.ibm.com> wrote:
Hi, Julie
I think it's time to consider the automation synchronization between Horizon source code and Transifex resources.
The general solution now in community is to use Jenkins jobs. Most of openstack projects use this method to synchronize their PoT files with Transifex resources.
There are two kinds of jobs: #1 A job after a commit event in git to generate PoT files and update Transifex resources if the PoT files are changed. #2 A regular job to download translations and create a gerrit review request to merge po files.
I think, it's no question for Horizon to use #1 to update Transifex resources automatically. How about #2 ? I remember originally Horizon team disabled automatics downloading because messy characters in po.en would cause broken in Horizon test. Now this issue has been resolved. So I wonder if Horizon would like to adopt #2 to enable the automatics translation downloading now.
Best regards Ying Chun Guo (Daisy)
Julie Pichon <jpichon@redhat.com> wrote on 2014/01/09 18:42:30:
Julie Pichon <jpichon@redhat.com> 2014/01/09 18:42
To
Ying Chun Guo/China/IBM@IBMCN,
cc
Subject
Re: [Openstack-i18n] Horizon patch with translation impact (havana)
Hello Daisy,
Thank you for your reply! Did you mean to send this email only to me? I think it would be useful to reply to the list to have the answer available in the archives, too - I'll be happy to resend my own answer as well.
"Ying Chun Guo" <guoyingc@cn.ibm.com> wrote:
Hi, Julie
The Horizon translation resources for Havana have been renamed with a prefix "Havana" in Transifex. The update is not automatic, both from source codes to Transifex and from Transifex to source codes. We could synchronize these resources with source codes. But we need to do it manually.
Understood, thank you for the information!
Although we don't have plan to update stable/havana translations, there is no stop for translators to do it.
Are there any plan to release a new version of Horizon stable? If there is, we can call for translators support to update translations.
There are 3 more Havana releases planned [0]. I imagine the string changes will be very minimal, more and more so.
Cheers,
Julie
[0] https://wiki.openstack.org/wiki/ StableBranchRelease#Planned_stable.2Fhavana_releases
Best regards Ying Chun Guo (Daisy)
Julie Pichon <jpichon@redhat.com> wrote on 2014/01/09 01:26:27:
Julie Pichon <jpichon@redhat.com> 2014/01/09 01:26
To
"openstack-i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org>,
cc
Subject
[Openstack-i18n] Horizon patch with translation impact (havana)
Hi,
I submitted a backport to Havana [0] that corrects a mistake in a help message, but I'm not quite sure if we're still planning on updating the stable/havana translations. If you don't feel it's appropriate in this case, please feel free to -1/-2 the patch. Thank you!
...Also if the discussions on the translation update schedules for stable and master have been summarised somewhere, please let me know. I can't recall the decided outcome.
Thanks,
Julie
[0] https://review.openstack.org/#/c/65506/
_______________________________________________ Openstack-i18n mailing list 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