14:04:28 #startmeeting releaseteam 14:04:29 Meeting started Fri Nov 27 14:04:28 2015 UTC and is due to finish in 60 minutes. The chair is dhellmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:04:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:04:33 The meeting name has been set to 'releaseteam' 14:04:51 our agenda is in the R-19 section at the bottom of the tracking etherpad 14:04:52 #link https://etherpad.openstack.org/p/mitaka-relmgt-plan 14:05:06 #topic actions from last week 14:05:13 #undo 14:05:14 Removing item from minutes: 14:05:31 courtesy ping Jokke_, ttx, dims, lifeless 14:05:35 #topic actions from last week 14:05:45 * Jokke_ to verify that it is safe to tag and then remove version entry from setup.cfg 14:06:13 I recreated my experiment and verified the results with lifeless, and used that to write the instructions I'll send today 14:06:17 * dhellmann determine which managed projects do not yet have reno integration completed 14:06:44 I've made the list, more on that in a bit 14:06:47 * dhellmann consolidate m1 sprint task list 14:06:59 see the first item under R-19 14:07:00 I'm still a bit unclear on how we should proceed, past the release.sh 14:07:15 especially around announcement 14:07:20 do you mean with the announcements? 14:07:22 ah, yeah 14:07:32 so let's talk about that in a sec? 14:07:52 * mordred to propose specific EOL dates for kilo and liberty 14:07:56 that's done and merged 14:08:01 sure 14:08:02 * ttx to summarize discussion of release models for projects that don't complete their work by the end of the cycle 14:08:10 done 14:08:14 you sent that email 14:08:15 k 14:08:19 still need to sweep through them 14:08:35 the open tag requests? 14:08:43 but would like to complete the stable-maint swap first 14:08:56 agreed 14:08:57 no, checking that all projects are using the right tags 14:09:06 ah 14:09:21 yes, maybe after the milestone 14:09:48 \o/ 14:09:58 I've updated the instructions email draft based on your feedback, https://etherpad.openstack.org/p/wUAtzSETGa 14:10:04 * mordred accomplishes things in release team 14:10:13 * dhellmann hands mordred a gold star 14:10:46 I tried to include some details about why the order is important, to avoid having people think "I can simplify this" and doing stuff in the wrong order and breaking CD 14:12:03 we still have several projects that haven't integrated reno: barbican, heat, manila, swift 14:12:23 I think I just saw new patches for manila this morning; I haven't looked for patches in those other projects, yet 14:12:50 I'm intending to hold the M1 tags until reno is at least added to the project repository and the project-config changes are submitted. Does that seem fair? 14:13:13 but would like things to stop moving first :) 14:13:14 dhellmann: you still around, 14:13:14 ? 14:13:24 ew, lag 14:13:25 here, I wonder if we're seeing freenode issues 14:14:14 I saw something about a DDoS earlier this morning on twitter 14:15:28 ttx: is this connection any better? 14:15:30 dhellmann: yes, fait 14:15:30 r 14:15:35 yep 14:15:49 looks good so far 14:15:51 ok, I'll use the direct connection for the rest of the meeting instead of my bouncer 14:16:31 since john has already told me he doesn't care for reno, I expect the swift team to avoid it. I'm not sure what we want to do if that happens. 14:16:55 I did set up the release notes link feature of the releases repo so the URLs can point anywhere, not just to reno docs. 14:17:07 thoughts? 14:17:43 the heat team just hasn't approved the patches to add it there https://review.openstack.org/#/q/topic:add-reno+project:openstack/heat,n,z 14:18:13 barbican seems to be having some issues with the patch: https://review.openstack.org/#/q/topic:add-reno+project:openstack/barbican,n,z 14:18:49 manila has submitted a patch and may need review help: https://review.openstack.org/#/q/topic:add-reno+project:openstack/manila,n,z 14:19:41 this lag is killing communication :-/ 14:20:24 ttx, you wanted to talk about how to handle announcements? 14:20:41 I'm going to work on the script we discussed monday morning, so it should be ready if we want to use it 14:23:56 * dhellman_ rejoins 14:24:48 ok, instead of fighting with IRC I'm going to close the meeting and send an email 14:24:51 #endmeeting