15:00:49 #startmeeting horizon 15:00:50 Meeting started Wed Apr 7 15:00:49 2021 UTC and is due to finish in 60 minutes. The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:53 The meeting name has been set to 'horizon' 15:01:09 hi everybody 15:01:13 o/ 15:01:15 hi all 15:03:37 o/ 15:03:54 let's wait two minutes more. I hope rdopiera will join us too 15:06:07 let's start 15:06:17 #topic Notices 15:06:58 next week OpenStack Wallaby will be released 15:07:15 it means I'm giving a PTL hat to vishalmanchanda 15:08:07 the week after it will be a PTG week 15:08:17 #link https://etherpad.opendev.org/p/horizon-w-ptg 15:09:06 do not forget to add topics you would like to discuss to our etharpad 15:09:08 #link https://etherpad.opendev.org/p/xena-ptg-horizon-planning 15:10:43 that's all updates from my side 15:10:48 do we cut another release for wallaby? 15:11:13 e0ne: you proposed several backports to wallaby (and I did some too) 15:11:28 amotoki: that's was my next topic 15:11:35 e0ne: okay 15:12:17 #topic Horizon Wallaby release 15:13:02 first of all, I want to ask all stable cores to be careful reviewing stable patches now 15:13:32 I saw few backports to stable/vicgtoria which wasn't in stable/wallaby 15:13:47 I didn't -2 on them because I proposed patches to stable/wallaby 15:14:14 good point. Perhaps I was confused around the branch cut of stable/wallaby. 15:14:38 amotoki: yes, it's a kind of usual confusing during such period 15:14:56 I was not aware of stable/wallaby at that time :( we need to be careful. 15:15:29 here is a list of proposed backports: https://review.opendev.org/q/status:open+AND+project:openstack/horizon+AND+branch:stable/wallaby 15:15:33 #link https://review.opendev.org/q/status:open+AND+project:openstack/horizon+AND+branch:stable/wallaby 15:15:49 I'm going to approve this one https://review.opendev.org/c/openstack/horizon/+/785133 15:16:04 it's proposed by amotoki and unblocks the gate 15:16:25 AFAIR, such approval is OK by our stable policies 15:16:32 yeah, all backports hit the failure of the integartion tests and it will unblock the gate. 15:16:37 e0ne: +1. 15:17:12 once all backports landed, I would like to cut a new wallaby release 15:17:48 I have one thing I would like to hear your opinion here. 15:17:52 it is about translation. 15:18:05 amotoki: sure, ask it 15:18:37 unfortunately the i18n team (zanata admin) have not setup a branch for wallaby on zanata yet. 15:18:48 so no translation happens for stable/wallaby. 15:19:18 we merged several translation imports for master but they were not applied to wallaby release 15:19:41 do we want to merge them back to stable/wallaby manually or release it as-is? 15:21:11 can we be sure that manual backports won't break anything? 15:21:37 I understand the importance of translations for horizon, but this sounds a bit risky 15:21:58 I believe so if we use gettext tooling lke msgmerge 15:28:08 According to my check, only ja and en_GB were updated after 19.1.0 release. 15:28:13 I used this command git log --stat 19.1.0.. | grep /locale/ | awk '{print $1}' | sed -e 's|.*/locale/||' | cut -d / -f 1 | sort -n | uniq 15:28:15 amotoki: how can we test that nothing will be broken? 15:29:03 what i think is to follow what the openstakc-zuul-jobs translation script does. 15:29:25 the ony difference is to pull translation from master 15:29:51 If a string is not included in POT, msgmerge command will drop such string. 15:30:17 sounds good 15:31:49 or we can just wait for stalbe-wallaby version on zanata 15:32:10 in either case, translators cannot update translations unless we manually backports them 15:32:27 so the final solution would be to create stalbe-wallaby version on zanata 15:32:47 amotoki: do you know any ETA for this? 15:33:17 e0ne: no at the moment. I send a reminder to openstack-i18n list but no response from the zanata admin (ian and andreas) 15:33:42 the reminder email was sent last week. 15:35:58 :( 15:41:07 languages impacted are ony ja and en_GB, so I think we can wait for zanata wallaby setup and do not backport them manually 15:41:17 I prefer to wait for zanata team 15:41:27 yeah, that's what I am thinking now 15:41:30 but I won't block community's decision on it 15:42:33 once zanata wallaby setup is doen and translation import statrs to work, we can cut a new release soon 15:43:19 if it does not happen soon, we can consider manualy updates as exception then, but it looks better to wait for zanata setup. 15:43:29 +1 15:45:23 vishalmanchanda, tmazur: any comments about translations an release in general? 15:46:04 e0ne: I think we should wait for zanata team 15:46:16 +1 15:47:29 do we want to raise it to openstack-discuss list too? 15:47:39 for more broader discussion 15:48:24 +1 15:48:25 amotoki: yes. 15:48:40 +1 15:51:25 amotoki: could you please send a mail once you're i18n core? 15:51:46 okay 15:53:00 amotoki: thank you 15:53:18 do we have anything more to discuss? 15:53:50 nothing from my side. 15:54:21 nothing from me too 15:54:58 I also would like to land https://review.opendev.org/c/openstack/horizon/+/783782 before another release for wallaby branch 15:55:25 we did not sync policy files from service projects. 15:55:38 amotoki: +1. we have to do it 15:56:28 amotoki: looks ok to me. just need to take a look at latest Patch set. 15:57:55 I hope someone ensures to handle the sync in the next release :) 15:58:21 It was done by me for past several releases but it is time to do it as a team. 15:58:52 don't worry I can do that. 15:58:55 let's add it to the release checkilst in our contributor or PTL guideline 15:59:38 we don't have such list now. let's create it. 16:00:23 agreed 16:00:33 let's do it for Xena release 16:00:37 we're out of time 16:00:49 we can continue in #openstack-horizon if needed 16:01:04 thanks everybody for your contributions to this release! 16:01:07 see you next week 16:01:14 o/ 16:01:16 Thanks everyone! 16:01:39 See you next week. 16:01:41 #endmeeting