Open Stack

On Mon, Sep 21, 2015, at 09:08 AM, Ying Chun Guo wrote:
> Hello,
> 
> Here is a new requirement.
> I want to consider branches while synchronizing between repo and 
> translation server.
> 
> For example, now the syncronization is between the master branch in repo 
> and the master version in Zanata.
> After liberty branch is created in repo, usually at the time when RC1 is 
> cut, 
> I will create the corresponding "liberty" version in Zanata.
> All the translations in Liberty should be made in "liberty" version,
> and the "master" version in Zanata will be opened for M release.
> 
> If I want to keep the sync both for master branch and liberty branch, 
> how many changes should make to the current infra files ? 
> Is it difficult to make the update ?
> 
The change to make this happen doesn't seem too difficult. I have pushed
a series of patches to do it starting with
https://review.openstack.org/#/c/225951/

In that series we basically handle the pushes to Zanata first as thats
easier, then follow up with making the jobs handle pushes to Gerrit, and
finally I chose oslo.versionedobjects to be the first project to get the
liberty jobs as it was the test project for the Zanata transition as
well. One thing to note is I haven't done this for Horizon or Django
OpenStack Auth as they are slightly different but it should follow the
same process.

If you want to look these over that would be great. Looking for feedback
on the process before we continue to plan for other projects like
Horizon. Hopefully this works as a good illustration of how this may
work.

One last thing to note, I think the versions in Zanata should match the
branch names in git. So we would want to have a version of
'stable/liberty' instead of 'liberty'. That makes the scripting slightly
easier and should make it clear what the mapping is between projects and
Zanata.

Clark