13:00:34 <ttx> #startmeeting releaseteam 13:00:34 <openstack> Meeting started Mon Oct 5 13:00:34 2015 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:36 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:39 <openstack> The meeting name has been set to 'releaseteam' 13:00:42 <ttx> dhellmann: o/ 13:00:55 <ttx> #link https://wiki.openstack.org/wiki/Release_Cycle_Management#Agenda 13:01:21 <ttx> #topic Release tag changes 13:01:22 <dhellmann> o/ 13:01:33 <ttx> dhellmann: I flagged a few reviews about release tag changes 13:01:41 <ttx> https://review.openstack.org/#/c/228461/ 13:02:09 <ttx> networking-ovn switching to -with-milestones 13:02:22 <ttx> They decide, right 13:02:40 <dhellmann> yeah, if they're happy with that model, it's ok 13:02:52 <ttx> If you post your +2 I'll approve it now 13:03:04 <dhellmann> done 13:03:36 <ttx> https://review.openstack.org/#/c/228511/ 13:03:51 <ttx> same for vmware-nsx 13:04:10 <dhellmann> voted 13:04:16 <ttx> armax temporarily -1ed, so i'll check that first 13:04:28 <dhellmann> looking at the one for ironic-python-agent they also ask for the managed tag 13:04:47 <ttx> oh, yeah, that was the managed bit 13:04:52 <ttx> ok approving 13:05:18 <ttx> https://review.openstack.org/#/c/229983/ 13:05:44 <ttx> ironic-python-agent asking for switch to intermediary + managed 13:05:50 <dhellmann> I'm looking at the other ironic projects and which are managed 13:06:26 <dhellmann> most of them are not, yet, and I wonder if that's an oversight or a difference in expectations 13:06:35 <dhellmann> jroll: ^^? 13:06:39 <ttx> maybe we can ask for precisions 13:06:49 <ttx> also that would likely kick in mitaka 13:07:12 <ttx> so might be better to make the change post-reolease so that it's clearer when that kicks in 13:07:23 <dhellmann> good ponit 13:07:28 <dhellmann> ok, I'll ask on the review 13:07:34 <ttx> at least the :managed side 13:07:46 <ttx> ok that works 13:07:58 <ttx> #topic Liberty release coordination 13:08:09 <ttx> We are at R-1 which is the last week to produce "normal" RCs 13:08:32 <ttx> I'm respinnin RCs to include last translations imports this week 13:08:45 <ttx> Most should be done by Wednesday 13:08:59 <ttx> After that the idea is to only respin on embarassing regressions 13:09:06 <ttx> and install / upgrade blatant fails 13:09:44 <ttx> The goal being to have a calm release week, and a busy Thursday retagging everything 13:10:00 <smcginnis> ttx: Cinder RC2 update - I need to check on one more review, but I think we may be ready for RC2. 13:10:12 <ttx> things following the intermediary model sure require less work 13:10:42 <ttx> smcginnis: we'll wait until tomorrow to catch the latest translations anyway 13:10:52 <smcginnis> ttx: Sounds good. Thanks! 13:11:24 <ttx> dhellmann: am I missing anything ? 13:11:43 <ttx> dhellmann: anything on the requirements side that may trigger unexpected requirements syncs ? 13:14:34 <dhellmann> k 13:14:35 <dhellmann> btw, your feedback on the schedule change to the project guide was good, I'll try to incorporate that in a new draft early this week 13:14:48 <ttx> ack 13:14:58 <ttx> #topic Open discussion 13:15:08 <ttx> Anything else we should be aware of ? 13:15:10 <dhellmann> looking at https://review.openstack.org/#/q/project:openstack/requirements+is:open+branch:stable/liberty,n,z 13:15:18 <dhellmann> I think there's some lag in my connection 13:16:08 <dhellmann> https://review.openstack.org/#/c/230744/1 would update a minimum, but I don't know how big of a deal that would be 13:16:16 <dhellmann> I went ahead and suggested only changing the constraints file 13:16:40 <ttx> hmm, let's see who consumes that 13:17:05 <dhellmann> we have some other constraints file changes we should update to ensure we're testing properly 13:17:28 <ttx> apparently muranoclient bump would not affect anything we handle 13:17:37 <dhellmann> I wasn't sure if we wanted to follow the single +2 rule during this period or not, so I left +2 but didn't approve 13:18:02 <dhellmann> yeah, that's not surprising -- do you want to allow it then? 13:18:31 <ttx> yeah, I think it's fine. Doublechecking master first 13:18:56 <ttx> not merged in master yet 13:19:08 <ttx> we should approve in master first, see what that triggers if anything 13:19:39 <dhellmann> sounds good, approving now 13:20:07 <ttx> still confused as to how a .patch bump can enable "everything they did in liberty" 13:20:45 <ttx> or rather "half of Murano functionality" 13:20:56 <ttx> must have been a hell of a bug 13:21:10 <dhellmann> sigh 13:21:41 <dhellmann> we need to have teams put in better functional testing for clients 13:22:16 <ttx> the constraints bump are ok, are you approving them? Should I ? 13:22:29 <dhellmann> I'll do the ones I didn't submit 13:23:04 <dhellmann> ttx: oh, well, I already +2 those -- do we want to follow the single reviewer rule right now? 13:23:07 <ttx> approved yours 13:23:17 <ttx> dhellmann: yeah, that's fine on constraints bump 13:23:21 <dhellmann> ok 13:23:30 <dhellmann> we hadn't talked about it, so I wasn't sure 13:24:04 <ttx> ok, anything else for the meeting ? 13:24:25 <dhellmann> do you need any help with the rc2s this week? 13:24:50 <ttx> I think I have them under control 13:24:54 <dhellmann> all of those constraints changes are approved 13:25:06 <ttx> I'll let you know if things go weird 13:25:12 <dhellmann> ok, let me know if I can help, otherwise I'm going to keep working on the conference presentation and mitaka communication plans 13:25:21 <ttx> ack 13:25:23 <ttx> #endmeeting