06:59:59 #startmeeting requirements 07:00:00 Meeting started Wed Jan 31 06:59:59 2018 UTC and is due to finish in 60 minutes. The chair is prometheanfire. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:00:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 07:00:03 The meeting name has been set to 'requirements' 07:00:09 #topic roll call 07:00:12 tonyb, prometheanfire, number80, dirk, coolsvap, toabctl, smcginnis 07:00:17 o/ 07:00:23 o/ 07:02:47 #topic controversies in the queue 07:02:54 #link https://gist.github.com/prometheanfire/f4e710363ebbe9a743753cfaec877847 07:03:11 that's my current list (subject to change) of what needs to get in before freeze 07:03:23 o/ 07:03:53 a couple of those are gating now, I was going to merge the rest into a single review (along with any that fail this morning) 07:03:57 I wonder whether the release team agrees that the uc changes for the new releases are not going in anymore? 07:04:08 I remember last time there was a discussion around "but if we release it, we want it" kind of thing 07:04:11 I've told them 07:04:22 they haven't said anything so far 07:04:26 ok 07:04:30 I can tell them again just in case 07:04:47 and going forward we don't take uc changes from other projects anymore by default? would be good to leave a -2 on the bot proposal patch 07:05:03 (other projects - any upload of new version to pypi) 07:05:11 ya, -2 for all 07:05:49 Dirk Mueller proposed openstack/requirements master: update constraint for oslo.serialization to new release 2.23.0 https://review.openstack.org/531788 07:06:16 prometheanfire: what about https://review.openstack.org/#/c/531788/ ? the oslo.serialization update seems to be popular (and we left out the previous couple of releases due to regressions) 07:07:23 iirc that should have been on the list 07:07:30 I'll add it now 07:08:15 (stuff older than a particular review was generally approved) 07:08:59 moving on then 07:09:02 one more q 07:09:05 ? 07:09:09 there are a couple of client releases in the queue 07:09:19 and the schedule says jan 22 - 28 "final clients release" 07:09:33 and even those released on jan 22 are not yet merged. I think we should take them 07:09:40 e.g. monascaclient (but there are others) 07:10:07 would be tough to argue that due to gate hickups people who release on time are out 07:10:12 I'll run it past releases to be sure, but ok 07:10:19 monascaclient was approved already 07:10:26 may not have been listed 07:10:38 oh, indeed. sorry 07:11:22 anyway, lets move on 07:11:29 but yes, I'll have releases go over the current queue to be sure 07:11:35 #topic ptg 07:11:41 I got nothin 07:12:35 me neither 07:12:51 me too 07:13:21 #topic election 07:13:40 I'm down for whatever 07:14:52 I think we have 3 most active members here 07:14:56 dirk? 07:15:38 I think prometheanfire you're doing very good. I kinda like your mails as well on the list 07:16:11 I haven't thought about yet 07:16:15 I thought the mr freeze quotes go well with the freeze theme 07:16:40 if we manage to pull of the non-global requirements then I think the run for an extra PTL might be unwarranted, it could be folded into releases or some other repo 07:17:11 although the original plan was that distros get more involved in this, it didn't really happen yet (and with people on the container bandwagon, maybe they also care less) 07:17:35 yay redhat lol 07:17:48 prometheanfire are you up for another turn, did I get that correctly? 07:18:16 I think it would be sort of difficult to have an election in a community of 3-5 active cores ;) we should just decide for somebody 07:18:30 I'm up for it 07:18:31 +1 07:18:38 wfm, +1 07:18:39 prometheanfire: +1 07:19:01 not sure about the next one after, real life will probably get busier around then 07:19:25 but I'll add myself to the repo soon then 07:19:26 thanks :D 07:19:43 #topic Open Discussion 07:20:08 nothing from my side 07:20:17 nothing here either 07:21:04 me too 07:21:21 #endmeeting