15:00:17 #startmeeting releaseteam 15:00:18 Meeting started Fri Dec 14 15:00:17 2018 UTC and is due to finish in 60 minutes. The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:22 The meeting name has been set to 'releaseteam' 15:00:36 o/ 15:00:48 ping - ttx dhellmann evrardjp diablo_rojo_phon 15:01:00 #link https://etherpad.openstack.org/p/stein-relmgt-tracking Agenda 15:01:10 o/ 15:01:11 Around line 202 15:02:04 o/ 15:02:10 #topic Outstanding Semver patches 15:02:11 o/ 15:02:13 #link https://review.openstack.org/#/q/status:open+branch:master+topic:sem-ver 15:02:22 I added this one 15:02:33 dhellmann: Wanted to take it away? 15:02:34 mostly I was thinking we should include a reminder in the next weekly update 15:02:51 I guess I could have just added that reminder right to the etherpad... 15:02:53 I'll do that 15:03:15 Works for me. 15:03:19 oh, well, there's no content at all in the r15 etherpad 15:03:28 or r16 for that matter 15:03:38 I skipped this weeks countdown since there wasn't much and it was a busy week. 15:03:50 Yeah, I need to get the template in the rest of them I think. 15:04:05 If you want to throw the note in there for now, I can get it formatted and updated with other things. 15:04:12 ok, I'll work on that 15:04:33 Some of those semver patches have had several rechecks and they keep failing from other issues. 15:04:44 Literally no code changes in them, so it should be OK. 15:05:32 it should be easy to review, wonder why people are not doing them? 15:05:32 dhellmann: Have you heard anything internally at Red Hat about anyone missing those bumps? 15:06:18 I haven't, but can ask 15:06:25 I'm not sure where we are in our testing phase right now 15:06:37 That's OK, I just think it's interesting that it hasn't been an issue so far. 15:06:40 should we rebase them so that it shows up on top of the people's list, or ping on the ML? 15:07:05 yeah, it's possible the QE team is still dealing with wrapping up rocky, so hasn't done much with the upgrade tests for stein yet 15:07:09 pining would be less of a resource hog 15:07:15 ++ 15:07:16 pinging* 15:07:29 * dhellmann pines for them, too 15:07:34 lol 15:07:39 :) 15:07:59 ok I will ping a few ppl 15:08:05 pining for the fjords? 15:08:17 for the semver patches 15:09:31 So plan is: ping some folks, add mention to next countdown email. 15:09:43 I will recheck some of those failing ones too. 15:10:02 notes added to https://etherpad.openstack.org/p/stein-email-r15 15:10:03 Maybe getting some more +1's on some of them might raise it up in some lists. 15:10:07 dhellmann: Thanks! 15:10:09 if it's too long, feel free to cut it back 15:10:47 I am just commenting who I pinged, it should help on seeing it 'changed' :) 15:10:51 we'll see 15:11:01 in the future, putting the sem-ver footer at the end of the commit message with the other footers is probably safer 15:11:13 fungi: Safer? 15:11:43 well, they're called "footers" because they're all expected to be in the final "paragraph" of the commit message, one-per-line 15:12:06 Ah, yeah. We did some tests though and verified this works. 15:12:22 But probably good in the future to try to keep it last. 15:12:22 mixing them into the middle of the commit message isn't technically correct, though pbr seems to honor it anyway 15:12:54 did we ever update the release machinery to add those automatically when we create the branches? 15:13:05 Yes, I believe so. 15:13:09 ok 15:13:54 Can't find it right now, but will double check that after the meeting. 15:14:11 #topic Release governance tracking 15:14:17 ttx: Want to take this one? 15:14:19 yes 15:14:25 I wanted to give a quick update 15:14:46 Been contacting all teams with corner-cases and processed most of them 15:15:12 We'll be left with a lost of deliverables that shall be considered "new" and reviewed around milestone-2 15:15:16 a list* 15:15:23 #link https://etherpad.openstack.org/p/UChiqxElUV 15:15:53 smcginnis : http://git.openstack.org/cgit/openstack-infra/project-config/tree/roles/copy-release-tools-scripts/files/release-tools/add_release_note_page.sh#n48 is the change 15:16:00 just waiting for answers from Heat, Horizon and Kolla 15:16:22 dhellmann: Thanks! 15:16:25 Once done I'll run the script again and triplecheck 15:16:28 Last line too. 15:16:36 Will clean it up and post it too 15:17:42 that's a lot of repos 15:17:54 yeah 15:18:33 Will create a storyboard story to track this work 15:18:59 Maybe e0ne is around to take a look at the horizon ones. 15:19:52 ttx, I'm sorry for the delay. I'll send you response tonight 15:20:23 So next steps are finalize with those few teams, recheck the data, then post it to the ML? 15:20:33 e0ne: it's fine, not really time-sesntive :) 15:20:51 smcginnis: https://storyboard.openstack.org/#!/story/2004616 15:21:10 smcginnis, ttx: we didn't release tempest plugin for rocky because there we no changes 15:21:14 adding tasks right now 15:22:50 e0ne: I think those shoud still probably be tagged even if it is the same sha as the last one. Just for tracking. 15:23:36 that is all I needed 15:23:50 #topic Moving meeting time 15:24:14 diablo_rojo is trying to get involved but current meeting time does not help 15:24:21 I'm free over the next hour 15:24:29 So etherpad says moving one hour later, but I think Tony had posed the question of moving it completely to another day so it isn't Friday night for some. 15:24:30 at least in winter time 15:24:36 7am in her vicinity 15:24:51 smcginnis: ok, will do it 15:25:02 ah, hm, ok. Maybe move to one hour later for now and then discuss moving to another day ? 15:25:03 I can move later in the day. I have meetings in that time slot over the next couple of weeks, but I can catch up after until those meetings are done. 15:25:03 Thanks e0ne! 15:25:27 we talked about tuesday, iirc 15:25:44 I think I would rather find a good time slot for all/most rather than moving it around multiple times. 15:26:06 Thursday would work well as far as finalizing any countdown email content. 15:26:13 hmm Thursday 1600utc is free here 15:26:13 But Tuesday would work too. 15:26:22 Tuesday is busier 15:26:28 I have conflict in this hour, so I am fine with moving later 15:26:36 That Thursday timeslot would be perfect for me 15:26:41 thursday 1600 wfm 15:26:50 * dhellmann wonders if it works for diablo_rojo_phon and tonyb 15:27:04 Not sure if that helps Tony, but it's at least a little later for diablo_rojo_phon 15:27:10 We likely won't get an answer. Can't be worse at least 15:27:29 yeah 15:27:55 I can propose a patch to switch it if folks so far think that would be a better time. 15:28:04 ack 15:28:08 Then we can use the review as a way to see if it works for most. 15:28:11 We can discuss in the patch anyway 15:28:12 ++ 15:28:20 while we're talking about meeting times... 15:28:31 #action smcginnis to propose meeting time change to Thursday 1600 15:28:43 evrardjp : diablo_rojo_phon and I are meeting this Monday at 1900 UTC to do some onboarding training. You're welcome to join if you like, although I know that's late. 15:28:58 Oh, great! 15:29:12 Just in the -release channel? 15:29:17 we haven't worked out any details other than the time, so we'll probably start there 15:29:26 hmm, I could try to be around. laptop couch tv setup probably 15:29:42 but that works 15:29:45 I was going to walk through some open reviews with her, like I did with anne 15:30:26 I still hope to record some videos to post to Youtube walking through doing some reviews. 15:30:45 Would be nice if we had a set of onboarding material to point people to. 15:31:10 @dhellmann: am also interested for the on-boarding training 15:31:16 dhellmann: thanks for the invite :) Will add to agenda 15:31:33 great, the more the merrier 15:31:58 #topic Ansible role releases 15:32:17 Who's was this? 15:32:21 I just added that one 15:32:38 we've had a few issues with ansible role releases in the last week because of confusion about which jobs count and where they should be set 15:32:40 should I be scared? 15:32:54 see https://review.openstack.org/616632 for example 15:33:13 I just wanted to make sure everyone was aware, since there was travel this week 15:33:18 Was this that the release jobs were defined in repo instead of in project-config? 15:33:30 Saw some notes, but haven't been tracking. 15:33:30 I'm not doing much to drive the fixes, other than trying to correct whatever bad advice they were given 15:34:20 so this was more of an informational note for the team than anything 15:35:08 Do they have the correct advice now? Or does something need to be figured out here yet? 15:35:20 it's not clear that they're accepting my advice 15:35:39 most of that conversation happened on the review 15:35:40 Maybe evrardjp can help? 15:36:03 there are 1-2 steps to fixing this 15:36:13 1. move the release job settings back into project-config 15:36:29 2. (possibly) update the release validation logic to look for the new release job for that new type of deliverable 15:36:46 I don't know what jobs run when an ansible role is released so I don't know what's involved in 2 15:36:59 And "look for the new release job" would be looking in the repo's .zuul.conf? 15:37:05 no 15:37:14 we don't want to encourage that by having the release validation look there 15:37:20 I didn't think so. 15:37:27 it may have a name different from the publish-to-pypi job we use for python packages 15:37:49 so it's more like what we have for xstatic or puppet modules, where there's actually a different type of thing that looks for a different project template 15:38:23 we would need to update this data structure: http://git.openstack.org/cgit/openstack/releases/tree/openstack_releases/project_config.py#n138 15:38:52 and possibly the schema, I don't remember if we validate those values with the schema or in code 15:38:57 I am curious of what they actively need -- I will ping on tripleO channel with the content of this conversation 15:39:03 thanks, evrardjp 15:39:55 it looks like we already support release types that don't have jobs, so if that's the case we just need to add the type 15:40:31 that's all I had on that one 15:41:02 #topic Open discussion 15:41:10 Anything else to go over today? 15:41:20 nope 15:41:23 not from me 15:42:04 OK, nothing more from me either. 15:42:11 Thanks everyone for being here. 15:42:20 o/ 15:42:26 #endmeeting