21:01:09 #startmeeting requirements 21:01:10 Meeting started Wed Mar 6 21:01:09 2019 UTC and is due to finish in 60 minutes. The chair is prometheanfire. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:01:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:01:12 #topic rollcall 21:01:13 The meeting name has been set to 'requirements' 21:01:22 tonyb, prometheanfire, number80, dirk, coolsvap, toabctl, smcginnis, dhellmann ping 21:01:25 o/ 21:01:50 \o 21:03:38 I guess that means it's just you and I ;P 21:04:01 #topic Any controversies in the Queue? 21:04:03 o/ 21:04:05 a couple I think :D 21:04:13 smcginnis: too late, time to sit in the corner :P 21:04:29 Dahwwww 21:04:39 Wow yeah that kinda exploded in the last 24 hours 21:04:58 let's start with requests 21:05:15 tonyb: you already commented, should I abandon with a 're-comment'? 21:05:19 I'm inclined to do so 21:06:01 prometheanfire: So I'm torn 21:06:11 prometheanfire: I don't think we can do what;s being asked 21:06:25 the bot doesn't sync anymore 21:06:32 prometheanfire: but Abhishek also hasn't followed the process 21:06:55 didn't cherry-pick? 21:07:08 prometheanfire: I think just abandoing it them is a little harsh 21:07:13 prometheanfire: Yeah 21:07:19 ya, that's why I haven't done so yet 21:07:43 prometheanfire: Let me check the delta's again 21:07:51 maybe comment, pointing to the story about it saying that we will close in a week if the status of that bug hasn't changed 21:07:54 k 21:08:23 next bad thing 21:08:34 limiting paunch 21:09:18 I think that's okay 21:09:21 kinda annoying to have to do it, but it makes sense if global-reqs becomes descriptive and not prescriptive on branch creation 21:09:24 tonyb: yarp 21:09:37 It'd be good to understand why it's breaking heat 21:09:51 and if there is some other part of the process that's missing there 21:10:18 the patch only updates g-r which implies that u-c is correct 21:10:45 tonyb: indeed 21:10:55 tonyb: what about the requests patches that only update gr? 21:11:04 I thought those were ok (ish) 21:11:43 prometheanfire: Yup that's probably okay as long as they followed the process 21:11:53 ok 21:11:56 next set? 21:12:19 sure 21:12:20 sqlalchemy-1.3.0 breaks neutron (only neutron via our cross tests, maybe more) 21:13:42 I don't think a fix can be in before freeze, we should probably freeze now 21:13:44 prometheanfire: any idea why 21:13:55 tonyb: discovered yesterday, been busy... 21:14:17 I did ping neutron people though (should probably submit a bug) 21:14:19 no response 21:14:48 okay I guess we just skip it and have the usual dumpster fire post freeze 21:15:22 ya 21:15:25 I'll see if I can work out what it is and ping the sqla maintainer 21:15:34 I imagine they'll backport the fix anyway 21:15:39 hopefully 21:16:11 smcginnis: stestr/ostestr? 21:16:33 Looking at that now. 21:16:53 Looks like a recent change in stestr broke the default run when kicked off via ostestr. 21:17:07 Another one? 21:17:07 smcginnis: ok, should we drop that from today's patch for now? 21:17:12 And as far as I can tell so far, only glance hasn't dropped ostestr in favor of stestr direct usage. 21:17:19 We could do that. 21:17:20 as in stestr 2.3.1 ? 21:17:26 tonyb: yep 21:17:30 I have an updated patch in glance to switch to calling stestr. 21:17:33 Pfft 21:17:35 tonyb: look at uc bot update 21:17:37 smcginnis: \o/ 21:17:48 And I think I have a fix ready in stestr, so the next one should hopefully be OK. 21:18:20 Oh fsck that's my fault :( 21:18:53 The fix is easy 21:19:01 Yeah 21:19:04 ok, I'll drop it from the uc bot patch, notify requests guy to cherry-pick the gr portion (and reafirming the denial of the uc portion) and review the paunch stuff 21:19:06 prometheanfire: you said you think they have a fix already? 21:19:22 tonyb: for? (not aware of anything) 21:19:35 smcginnis: should that version of stestr be masked? 21:19:38 prometheanfire: the stestr 2.3.1 bug? 21:19:52 tonyb: nah, was just going to drop it from the uc bot update 21:20:01 prometheanfire: Okay 21:20:13 * prometheanfire has been traveling today 21:20:21 prometheanfire: but it wont get fixed if we don't tell them so I'll do that 21:20:25 Well, it's only an issue if still using ostestr. And we've been saying to get off of ostestr for awhile, so maybe we don't want to mask it as extra ammo to get folks to update. 21:20:34 tonyb: I thought smcginnis was handling it 21:20:46 Yep, got it 21:20:53 smcginnis: I'm fine with proding them 21:20:55 smcginnis: Ahh okay 21:21:06 Here's glance update: https://review.openstack.org/#/c/578529/ 21:21:17 And I should have an stestr PR as soon as we're done here. 21:21:26 smcginnis: cool 21:22:13 anything else from the queue? 21:22:40 not from me 21:23:08 Nothing from me. 21:23:28 k 21:23:37 #topic ptl stuff 21:23:45 it's election time 21:24:14 prometheanfire: that it is 21:24:30 I'm always open to new people, the more people running the better 21:24:49 prometheanfire: sure I don't think we have any new people ;P 21:24:55 yep 21:25:21 I can stay on (everywhere I've applied/asked has been happy about it) 21:25:36 even the secrete one, heh 21:26:00 longer term we should look to merging with the stable team (maybe that'll be a topic) 21:26:27 theer isn't a stable team to merge with 21:26:31 a topic for the ptg that is 21:26:35 tonyb: stable/releases 21:26:36 It could help for hiring, so happy to see you continue on. 21:26:43 smcginnis: it has 21:27:11 one place may send me to the ptg portion (since I'll be gone for the summit) 21:27:20 prometheanfire: perhaps but we split off from releases after Austin because even though there was overlap there was too much to do for one PTL 21:27:28 ok, I'll officially announce sometime this weekend (need to look at the election timeframe) 21:27:47 tonyb: ah, that's a good point 21:27:47 I think the 12th is the nomination deadline. 21:28:04 Yep, 6 days, 2 hours to go. 21:28:04 smcginnis: ok, so the weekend is good 21:28:06 smcginnis: correct 23:45 March 12 (UTC) 21:28:54 #topic summit/ptg 21:29:04 * prometheanfire already stated his ability 21:29:07 Maybe good to have a PTG topic to talk about if that still makes sense, but I think it's probably good still having the separation of concerns. 21:29:14 even if someone doesn't send me I might try and come anyway 21:29:17 for the summit I submitted the 'requirements-libs' thing as a forum session 21:29:22 smcginnis: ack 21:29:29 tonyb: cool 21:29:54 smcginnis: Yup we can hijack a release session to discuss that 21:30:22 prometheanfire: If you don't have a company paying, I'm willing to make sure you don't go thirsty. 21:30:34 \o/ 21:30:50 smcginnis: lol, I did submit for aid as well, which I think is announced on the 15th 21:30:56 * tonyb can probbaly help with that too 21:31:20 Based on others that have received travel assistance, I would definitely hope it's not even a question that you will get it. 21:31:30 we can take that part offline, but I have the flight covered at least 21:31:38 ++ 21:32:02 ++ 21:32:09 anything else for the ptg? 21:32:27 prometheanfire: Just the planning etherpad 21:32:34 prometheanfire: so nothing specific 21:32:37 https://etherpad.openstack.org/p/DEN-requirements-topics ? 21:32:55 looks like 21:32:57 #link https://etherpad.openstack.org/p/DEN-requirements-topics 21:33:05 prometheanfire: yeah that one ;P 21:33:29 ok 21:33:34 #topic open floor 21:33:58 nada 21:34:19 Ah, stestr deal is already fixed - https://github.com/mtreinish/stestr/commit/ac8dac07f5faa487254c649e7411515616392403#diff-e77977ac6a427e77fc880ed584215c86 21:34:34 Last night (at least for my time) 21:34:48 \o. 21:35:16 so we just wait for 2.3.2 ;P 21:35:18 #endmeeting