15:00:10 #startmeeting releaseteam 15:00:11 Meeting started Fri Oct 20 15:00:10 2017 UTC and is due to finish in 60 minutes. The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:15 The meeting name has been set to 'releaseteam' 15:00:21 Ping list: dhellmann, dims, fungi, tonyb, lbragstad, ttx 15:00:28 o/ 15:00:43 lbragstad: Morning lbragstad. Snow up there yet? 15:01:29 not yet 15:01:39 Soon enough I'm sure. :) 15:01:43 oh yeah 15:02:00 bow hunting on sunday morning and it's going to be in the 30s 15:02:38 Too brisk for me to sit in the woods without a campfire. 15:03:02 :) 15:03:11 I think everyone is getting back from travelling, meetings, and power outages, so I'll wait a while. 15:03:32 If no one else can make it, I guess I can just record an update and end early. 15:03:57 sounds good - queens-1 is due today, yeah? 15:04:31 Well, technically yesterday, but we can't really release anything right now so that buys some time. 15:04:46 oops sorry 15:04:53 travel day 15:04:57 ah - we're still waiting no three patches in keystone, hoping to cut it today 15:05:17 lbragstad: OK, as soon as you can get the release request in, that would be good. 15:05:25 ttx: No worries, knew you were on the move. 15:05:41 dhellmann was tied up with another meeting earlier. 15:06:04 fungi had his power cut. I'm sure he's been paying his bills. :) 15:06:51 Guess I'll just give an update then if it's just us. 15:06:58 do we have anything on the agenda ? 15:06:59 The usual etherpad: https://etherpad.openstack.org/p/queens-relmgt-tracking 15:07:02 ok 15:07:07 ttx: Not much, this shouldn't take long. 15:07:18 #topic Zuul changes for release jobs 15:07:35 We've been working through some changes that are preventing us from releasing anything. 15:08:08 We've gotten pretty close. Just need a test release to be re-enqueued to see if the last changes addressed things. 15:08:42 Hopefully once fungi is able to get back online he can help with that since no one else seems to be jumping on my request to help. :) 15:09:05 Then we can start releasing again as normal on Monday. 15:09:05 you have a tracker for those issues? 15:09:26 I think I saw an etherpad link flying earlier 15:09:32 Most were being tracked in the infra zuul etherpad, but I just started this one this morning: 15:09:35 https://etherpad.openstack.org/p/release-job-failures 15:09:39 ack 15:09:59 Last one there just happened from another job, so not sure the impact of it yet. 15:10:12 Might just be the next roadblock we run into after we get past the last one we hit. 15:10:55 o/ 15:10:58 So there will likely be some activity in the -infra channel today towards that, but I will try to leave updates in -release just so it's easier to get the current status. 15:11:16 dhellmann: Just giving an update on the release issues. Anything you want to add? 15:11:25 reading the backlog 15:11:56 I think that covers everything. 15:12:01 OK, great. 15:12:11 I'm in and out again today, so if we can find someone from infra to help debug that job failure that would be good 15:12:51 I'm hoping we can get some help there. I'm not sure where to start with that last one. 15:13:11 #topic Targeting release plan tasks 15:13:29 This one is more of a question from me. We have our list of things: 15:13:29 sorry that I could not help more this week with all the traveling and conferecing 15:13:38 #link https://etherpad.openstack.org/p/queens-relmgt-plan 15:13:47 it's just hard to keep tabs on others progress while on the road 15:13:59 ttx: Yeah, been there. No problem. 15:14:09 you just end up duplicating effort and not helping 15:14:45 Just wondering with the tasks we signed up for if we should be targeting some of them to when we want to try to get them done. Or if there is some other way we've tried to track progress to keep those tasks moving. 15:15:07 yes, targeting to milestones helped in the past 15:15:21 * ttx checks pike-1 tasks 15:15:28 ++ for targets 15:15:37 queens-1 I mean 15:16:16 So should we go through and tag some of them to call them out for queens-2? 15:16:36 yes, review your tasks and add words 15:16:48 where you plan to work 15:17:17 #action team to review Queens plan tasks and add milestone they plan to complete them by. 15:17:19 I'll do that early next week 15:17:35 OK, just wanted to bring that up. 15:17:40 #topic Open Discussion 15:17:50 Anything else we need to go over this week? 15:18:31 nothing urgent 15:18:59 OK, then I'll keep it short. 15:19:03 Thanks everyone. 15:19:05 smcginnis : do you feel like this week has given you any insight into the jobs? 15:19:09 how they work, etc.? 15:19:28 sort of throwing you into the deep end of the pool 15:20:00 It's certainly helped to start to dig into some of it. 15:20:12 I at least now know more of what I don't know, so I see that as progress. 15:20:18 cool 15:20:34 I'm wondering how we can document this stuff better 15:20:43 We certainly have a lot of moving parts in a lot of different places. 15:21:10 It would be good to somehow pull that into a consumable format to help see the big picture. 15:21:32 do we have a place for the release team to write documentation that doesn't show up on releases.o.o? I'm not even sure where I would put a description of those jobs. 15:21:33 I'll ponder that idea and see if there's anything I can start for that. 15:21:44 maybe the infra manual? 15:21:49 Yeah, we almost need our own "dev-ref" section. 15:22:12 Yeah, maybe infra manual would work. 15:22:18 if we start a new release-team repo with a sphinx build we could move our process document there, too 15:22:58 Doesn't sound like a bad idea. But I do think having that (PROCESS.rst) in the repo can help others discover it. 15:23:05 ok, let's think about where we want that and who the audience is 15:23:06 if we're going to move the jobs into the releases repo, we will want them documented better anyway 15:23:13 Though if we had a dedicated documentation location that would probably be better. 15:23:21 And just mention it in the README. 15:23:29 so maybe doing it right there in the tree but publishing it separately from releases.o.o is the right thing to do 15:23:35 Good point about the jobs too. 15:23:58 a general picture of the various jobs and commands used would be nice 15:24:01 the releases.o.o publishing job is already custom, so we could move the source files for that to a new location and use the regular sphinx job 15:24:04 for regular docs 15:24:08 (and the various pipelines) 15:24:19 Yeah, let's let that simmer. 15:24:25 ++ for cogitation 15:24:35 because every time I dive into the jobs I have to rebuild that mental picture 15:24:56 Oh, it's a post job on releases, not a release-post job 15:24:57 I would like to be able to swap out the pages that hold that stuff so I can learn something new :-) 15:25:01 that sort of things 15:25:24 ++ 15:25:39 OK, anything else? 15:25:47 so let's get the jobs working, then we can move them and break everything again! 15:25:54 that's it from me 15:25:56 Haha, yep. :) 15:26:23 OK, thanks everyone. Let's hope next week is a little more relaxed. 15:26:36 #endmeeting