15:00:58 #startmeeting stable 15:00:58 Meeting started Tue May 31 15:00:58 2016 UTC and is due to finish in 60 minutes. The chair is tonyb. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:03 The meeting name has been set to 'stable' 15:01:16 Anyone here for the stable meeting? 15:02:06 it's a holiday in the US so perhaps only me and the Europe folks? 15:07:09 o/ 15:07:37 tonyb: no longer a holiday in the us now 15:08:25 ttx: okay. 15:09:53 ttx: Is there anything you'd like to discuss? 15:09:59 nothing pressing 15:10:22 tonyb: looks like we have a pretty good process laid down now 15:10:44 ttx: Yeah I think mostly it's working okay. 15:11:09 o/ 15:11:13 I have one thing 15:11:23 ttx: the biggest "problem" is deciding what from the big tent to include on the grand kilo EOL 15:11:31 ihrachys: hey! 15:11:38 ihrachys: please go ahead 15:11:54 tonyb: re kilo, why not drop it globally? :) 15:12:22 so my thing is, I finally have a document for proactive backporting process: https://review.openstack.org/#/c/322273/ 15:12:35 that could make use of some attention from core stable folks 15:12:43 ihrachys: because that isn't what's happend in the past. 15:12:45 note it's proposed for project-team-guide 15:13:01 so I tried to stay generic in wording 15:13:07 even though atm it's neutron thing 15:13:20 ihrachys: some clients like to stay "open" 15:13:33 I have people interested in the process for other projects, so... 15:13:54 ihrachys: I'll review it soon 15:13:56 ihrachys: Yeah I had your project-team-guide on the agdenda to bring up for awareness 15:14:00 tonyb: got it. don't they have any functional tests that would require other components? 15:14:10 thanks folks :) 15:14:20 ihrachys: I'll review it today (technically it's Wednesday here) 15:14:46 ihrachys: Yeah some do and that where tha ball of string starts to unravel 15:15:12 ihrachys: originally I had a list + devstack + requirements 15:15:38 ihrachys: which effectivly means EOL'ing anythign that has a hard requirement on those projects IIUC 15:16:39 leaving just unit tests and pep8 15:16:45 I want to avoid bugging infra too much but I think I just need to send the list and the proposed process and see what happens 15:17:13 when will those get dropped? do we set some counter? 15:17:32 ihrachys: Yeah, the part I'm most worried about is missing something and leaving the gate full of -1's from jenkins 15:18:09 meh. I would claim it's not supported across the board and move on. 15:18:26 ihrachys: IIUC infra will at some point stop running any tests on the kilo branches but I don't have a clear idea of when that'll happen 15:18:45 ihrachys: You're right I'm probably over thinkign it :D 15:19:06 tonyb: maybe you are not if we don't have it as a policy. 15:19:21 #action tonyb drop kilo ASAP 15:19:28 tonyb: at least for next time we need that, I would prefer we have a consistent message for all projects. 15:20:13 ihrachys: Yeah. I'm tryign to follow what we did for juno and apply that to kilo+big tent 15:21:48 fair enough 15:24:35 Anything else? 15:25:20 tonyb: maybe for future meetings we could try to get agenda / attendance beforehand and skip if we don't have topics/quorum 15:25:30 that would avoid keeping you up for little value 15:25:58 ttx: Yeah Normally Matt runs this meeting but he's on vacation 15:28:18 ttx: we did have an agenda but it's mostly boiler plate that I skipped as it was the 3 of us 15:28:49 anyway if there is nothgin else I'll call this done ... 15:29:31 You shall 15:30:06 Thanks ttx and ihrachys 15:30:09 see you round 15:30:14 #endmeeting