<html><body>
<p><tt><font size="2">Clark Boylan <cboylan@sapwetik.org> wrote on 2015/09/22 01:29:25:<br>
<br>
> From: Clark Boylan <cboylan@sapwetik.org></font></tt><br>
<tt><font size="2">> To: openstack-infra@lists.openstack.org</font></tt><br>
<tt><font size="2">> Date: 2015/09/22 01:33</font></tt><br>
<tt><font size="2">> Subject: Re: [OpenStack-Infra] Considering branches in the sync <br>
> between repo and Zanata</font></tt><br>
<tt><font size="2">> <br>
> On Mon, Sep 21, 2015, at 09:08 AM, Ying Chun Guo wrote:<br>
> > Hello,<br>
> > <br>
> > Here is a new requirement.<br>
> > I want to consider branches while synchronizing between repo and <br>
> > translation server.<br>
> > <br>
> > For example, now the syncronization is between the master branch in repo <br>
> > and the master version in Zanata.<br>
> > After liberty branch is created in repo, usually at the time when RC1 is <br>
> > cut, <br>
> > I will create the corresponding "liberty" version in Zanata.<br>
> > All the translations in Liberty should be made in "liberty" version,<br>
> > and the "master" version in Zanata will be opened for M release.<br>
> > <br>
> > If I want to keep the sync both for master branch and liberty branch, <br>
> > how many changes should make to the current infra files ? <br>
> > Is it difficult to make the update ?<br>
> > <br>
> The change to make this happen doesn't seem too difficult. I have pushed<br>
> a series of patches to do it starting with<br>
> </font></tt><a href="https://review.openstack.org/#/c/225951/"><tt><font size="2">https://review.openstack.org/#/c/225951/</font></tt></a><br>
<br>
<tt><font size="2">Thank you for the quick response.</font></tt><br>
<tt><font size="2"><br>
> <br>
> In that series we basically handle the pushes to Zanata first as thats<br>
> easier, then follow up with making the jobs handle pushes to Gerrit, and<br>
> finally I chose oslo.versionedobjects to be the first project to get the<br>
> liberty jobs as it was the test project for the Zanata transition as<br>
> well. One thing to note is I haven't done this for Horizon or Django<br>
> OpenStack Auth as they are slightly different but it should follow the<br>
> same process.</font></tt><br>
<br>
<tt><font size="2">Liberty translation plan includes Horizon, Django OpenStack Auth and Nova.</font></tt><br>
<tt><font size="2">Today Nova will cut its RC1 and I will create the corresponding version in nova,</font></tt><br>
<tt><font size="2">and ask our translators to work with the "liberty" version.</font></tt><br>
<tt><font size="2">Horizon's RC1 will be happened in this week too.</font></tt><br>
<br>
<tt><font size="2">I hope the jobs handle pushes to Gerrit could be ready by Oct.4. Because liberty</font></tt><br>
<tt><font size="2">translations are planned to be merged around Oct.5. If the jobs are not ready, </font></tt><br>
<tt><font size="2">manually import translations might need to be done.</font></tt><br>
<tt><font size="2">I don't have any timeline for the jobs handle pushes to Zanata .Because after RC1, </font></tt><br>
<tt><font size="2">it is "strict string freeze", string changes are not allowed to liberty branches.</font></tt><br>
<tt><font size="2">But anyway, you could set up your plan. I just hope jobs handle pushes to Gerrit </font></tt><br>
<tt><font size="2">ready on time.</font></tt><br>
<tt><font size="2"><br>
> <br>
> If you want to look these over that would be great. Looking for feedback<br>
> on the process before we continue to plan for other projects like<br>
> Horizon. Hopefully this works as a good illustration of how this may<br>
> work.<br>
> <br>
> One last thing to note, I think the versions in Zanata should match the<br>
> branch names in git. So we would want to have a version of<br>
> 'stable/liberty' instead of 'liberty'. That makes the scripting slightly<br>
> easier and should make it clear what the mapping is between projects and<br>
> Zanata.</font></tt><br>
<br>
<tt><font size="2">I understand a same version name could make easier. </font></tt><br>
<tt><font size="2">Yet Zanata doesn't support "/" in version name.</font></tt><br>
<tt><font size="2">Because version name is part of the resource URL.</font></tt><br>
<tt><font size="2">Do you like to use another character instead like "stable-liberty", </font></tt><br>
<tt><font size="2">or just use "liberty"?</font></tt><br>
<tt><font size="2"><br>
> <br>
> Clark<br>
> <br>
> _______________________________________________<br>
> OpenStack-Infra mailing list<br>
> OpenStack-Infra@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a><br>
> <br>
</font></tt></body></html>