13:00:26 <eumel8> #startmeeting openstack_i18n_office_hour
13:00:27 <openstack> Meeting started Thu Aug 16 13:00:26 2018 UTC and is due to finish in 60 minutes.  The chair is eumel8. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:28 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:30 <openstack> The meeting name has been set to 'openstack_i18n_office_hour'
13:00:42 <eumel8> #topic Open Discussion
13:00:46 <eumel8> hello
13:01:10 <jpich> Hello, hello
13:05:15 <eumel8> hello jpich :)
13:05:47 <jpich> :)
13:10:00 <jpich> eumel8: I see there's a stable-rocky branch in Zanata for tripleo-ui even though the project hasn't branched yet. I'm trying to understand the next step. I think when the project branches, we'll need to submit a translation job patch ourselves to tripleo-ui and that should update stable-rocky in Zanata as well?
13:10:22 <jpich> I hope there won't be too many string changes on rocky, cycle-trailing projects tend to stay in flux a little bit longer
13:10:54 <eumel8> yeah, just checked what's going on with tripleo
13:15:18 <eumel8> jpich: similar here: https://review.openstack.org/#/c/590364/
13:15:33 <eumel8> but the job name are changed this week
13:15:41 <jpich> oh
13:16:04 <jpich> do you know why the branch was created early this time?
13:17:05 <eumel8> I was enforced to do this ;)
13:17:16 <jpich> hah :) Is it going to be that way from now on?
13:18:08 <eumel8> I was also a little bit surprised
13:18:32 <eumel8> but for tripleo-ui job name is translation-jobs-master-stable, that means stable and master translation will sync
13:19:00 <jpich> Ok so nothing to do once the stable/rocky branch is created, all happens magically??
13:19:09 <eumel8> if no stable/rocky branch in repo, the job will fail until the branch exists
13:19:39 <eumel8> yes, magic, as usually
13:19:41 <jpich> That's cool at least :) Hopefully the first string upload won't just updates half the strings on zanata, heh! I think most of the features merged already at least
13:20:12 <jpich> It's pretty cool if no one has to do the repetitive job of adding a million translation-job-rocky etc every release :)
13:21:03 <eumel8> yes, because often I've overseen a repo in projects.yaml or Zanata. Now you have everything - or nothing :)
13:22:13 <eumel8> nevertheless you need one merge for a new stable version in project templates. I'm not sure if it would better to have translation jobs in project repo. Technically it's possible
13:23:01 <amotoki> hi
13:23:07 <jpich> If it can be done for all the projects in one place it seems fair. Easier for projects to keep up and not forgot to update the jobs too :-)
13:23:12 <eumel8> hi amotoki
13:23:24 <amotoki> it would be really nice if a branch creation in zanata automatically regardless of the timing of branch creations
13:23:55 <amotoki> there are too many projects for i18n team to track the situation now
13:24:22 <eumel8> that's true, I want to check Zanata API again if it's possible
13:25:02 <amotoki> in addition, there is no solid way to know which repos will have stable/xxxx branch.
13:25:48 <amotoki> cycle-with-milestone repos will have stable/branch, but it is not necessarily true for cycle-with-intermediary. some of them are not branched...
13:26:04 <jpich> cycle-trailing tend to branch a few weeks later
13:26:59 <amotoki> yeah, that's true. cycle-trailing projects usually? always? cut a branch a few weeks later.
13:27:16 <amotoki> if it is "always", the thing would be simpler.
13:28:09 <jpich> I think for tripleo it's been always :) In the past we were too optimistic and branched too early a couple of times, and it was really painful to manage the amount of backports for the RC
13:29:50 <eumel8> I have a loop around project list: curl -s -o /dev/null -w "%{http_code}" https://github.com/openstack/${i}/tree/${RELEASE}
13:30:20 <eumel8> if  http_code is not 404 there is a release branch ;)
13:30:57 <jpich> What do you use it the results for? Was it to decide when to create zanata branches?
13:32:36 <eumel8> currently it's only for updating the translation dashboard in Zanata. Looking for new project branches every morning and update the board manually
13:32:52 <eumel8> there are only 2-3 projects left with a master branch
13:33:35 <amotoki> eumel8: what happens when we create a stable version in Zanata before a corersponding stable branch is cut?
13:34:51 <jpich> eumel8 said the job would fail until the branch exists. It's the situation for Rocky tripleo-ui at the moment, looks like
13:35:28 <amotoki> so, there seems no downside from the point of view of job healthiness
13:35:59 <eumel8> amotoki: nothing. the Zuul job will fail if there is no stable branch. Translations are still in Zanata until the the branch is setup, then it will breakout
13:36:05 <jpich> I'm trying to check the openstack-health dashboard but getting API errors
13:36:16 <amotoki> the downside would be that there will be possible translation differences between master and stable-rocky...
13:37:02 <jpich> Yeah, my only concern is if there are features or other major changes to strings that merge before stable/rocky is created. If translators focused on stable-rocky in Zanata they may have to redo the work...
13:37:38 <jpich> This cycle seems ok but I know for tripleo-ui there has been others where we were pretty late with merging stuff, compared to when other projects had their stable branches and RC ready
13:38:12 <eumel8> amotoki: that's the reason why I normally would wait with Zanata versions until the repo branch is there. On the other hand stable version will merge to master back after release, so no translations get lost
13:38:45 <amotoki> tripleo is a project with cycle-trailing, so we can handle cycle-trailing projects differently
13:39:14 <amotoki> most cycle-with-milestone/intermediary projects are expected ot have stable/rocky so far
13:39:28 <amotoki> having stable-version would not be a problem for them
13:39:28 <jpich> yeah it's just if the strings changed a lot between the time stable-rocky is created in Zanata and stable/rocky is created in the repo. There won't be any updates in between. The translators may have to redo some work, or think they're at 100% when there's a big update still coming
13:40:36 <eumel8> jpich: when would you expect stable/rocky for tripleo-ui?
13:41:57 <jpich> eumel8: From what I can gather from the meetings, the goal is "soon", as soon as possible but it's difficult to predict. There are major CI issues at the moment that are preventing work from merging, in addition
13:43:32 <eumel8> jpich: yeah, got it on the mailing list. Somehow a nightmare
13:44:14 <amotoki> re: difference in master and a stable branch, in most cases, projects tend to avoid big changes before releases to avoid unexpected behavior in the stable branch.
13:44:32 <amotoki> so I believe the timing of branching would not be a problem in general
13:45:33 <jpich> I'm assuming we're not talking about cycle-trailing, because our "before release" is a bit different :-) Especially for tripleo-ui - we're dependent both on features being implemented in the main projects, then being added to the tripleo backend, AND then the necessary GUI parts for it can be merged at last
13:45:46 <jpich> even if the patches are ready earlier before the rest merge, it makes the project very prone to FFEs
13:48:42 <amotoki> I see, so can not small number of changes happen in the master branch before cutting a stable branch?
13:51:00 <jpich> sure but that doesn't mean in a lot, because cycle-trailing can release up to 3mo after the rest of the project, so the stable branch might be cut at any time long after the other projects
13:52:38 <amotoki> it seems better NOT to create stable branches for cycle-trailing projects in the same timing of cycle-with-milestone/intermediary.
13:53:16 <amotoki> the number of cycle-trailing projects are not big (note that I do not mention the number of repos)
13:53:45 <jpich> I would tend to agree. I think last time that was discussed during a PTG, the role of the i18n liaison for the cycle-trailing project was to help keep i18n PTL and translators up to date with that kind of information - when to expect string freeze, when is stable branch created
13:54:13 <jpich> I'm aware of two, though I forgot the other one now :-) For TripleO only tripleo-ui is translated for now, afaik
13:55:15 <amotoki> +1
13:56:11 <amotoki> so our current question is how we should handle stable-rocky version of tripleo-ui.
13:56:19 <amotoki> is there any conclusion now?
13:57:07 <jpich> I think the branch is here already so it is what it is, no point in deleting and recreating it. I believe there shouldn't be major changes this time around until stable/rocky is created in repo but... don't be angry with me if I'm wrong :-)
13:57:33 <jpich> it'd be good to rediscussed automated creation of zanata branches before stable-stein gets created in 6mo, so we don't end up with the same questions :)
13:57:46 <amotoki> no worries :)
13:57:47 <amotoki> +1
13:59:16 <eumel8> jpich: hopefully ;)
13:59:35 <jpich> thanks for sharing your thoughts amotoki!
13:59:42 <eumel8> thanks amotoki, jpich
13:59:51 <jpich> thanks for letting me ramble, eumel8 :D
14:00:05 <eumel8> rofl
14:00:25 <eumel8> lets see if channel topic is not damaged
14:00:30 <eumel8> #endmeeting