14:00:41 #startmeeting releaseteam 14:00:41 Meeting started Fri Jan 15 14:00:41 2016 UTC and is due to finish in 60 minutes. The chair is dhellmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:43 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:45 The meeting name has been set to 'releaseteam' 14:01:02 ttx, dims: ping 14:01:23 our agenda is under week R-12 in the etherpad 14:01:25 o/ 14:01:27 #link https://etherpad.openstack.org/p/mitaka-relmgt-plan 14:02:03 #topic actions from last week 14:02:13 #info dhellmann to talk with infra about moving release-tools scripts into project-config 14:02:40 we've had a couple of conversations, and I think the path here is more clear than it was 14:02:57 I started preparing changes to the scripts to make them a bit more stand-alone 14:03:09 #link https://review.openstack.org/267161 refactor list_deliverable_changes.py prior to move to project-config 14:03:09 #link https://review.openstack.org/267162 refactor script for commenting on launchpad bugs prior to move to project-config 14:03:09 #link https://review.openstack.org/267166 default to sending mail directly via lists.openstack.org 14:03:15 I had a question about that 14:03:55 ok 14:04:08 My understanding was that things needed to move to project-config because the jobs would run on privileged nodes 14:04:31 yes, that's part of what needs to change 14:04:33 but that usual unprivileged jobs could import code more easily 14:04:46 yes, that's my understanding, too 14:05:20 what requires privileges in the tagging code ? 14:05:38 the part that accesses the gpg key for signing the tag 14:05:40 signature 14:05:59 and there's the launchpad update, too, that has credentials 14:06:14 is there a way to split it between privileged and unpriviliged 14:06:18 hmm 14:06:27 the signing? 14:06:33 ah, that's probably what I missed 14:06:41 that release script is pretty simple already 14:07:04 I figure the version we move to project-config won't call out to announce.sh, but that's the only other major change I see us making 14:07:13 oh, we need to remove the virtualenv bits, but that's a small thing 14:07:48 hmm ok, let me check that review again 14:07:49 so as you pointed out earlier this week, we'll have the parts that trigger the release run on a secure node, and the parts that announce the release after it is built run on a regular node 14:08:27 jeblair pointed out that the regular node may not always send email if the job ends quickly, so I have a change to push announcements through lists.openstack.org directly 14:09:12 ok, I was wondering why the launchpad lib stuff had to move too, but I guess that makes sense (requires creds too) 14:09:18 right 14:09:32 and there are system packages for that lib, so it shouldn't be a problem to move it 14:09:38 that review triggered all my DRY warning 14:09:44 ok, will re-review then 14:09:48 thx 14:10:04 yeah, it's unfortunate, but I don't see a good way around it 14:10:35 even if we release a library, we have to have system packages to install it on the secure nodes 14:10:39 and it's not *so* much code 14:11:20 ok, moving on? 14:11:30 #info ttx look into recovering tools we deleted that are still needed for kilo releases (done) 14:11:57 did you find any? I don't see any reviews to recover anything 14:12:20 yeah, so I walked through the process with Daviey and it's fine 14:12:27 ok, good 14:12:34 only using process_bugs from release-tools 14:12:40 and upload-release 14:12:53 do we need to update some documentation? 14:13:04 no 14:13:07 ok 14:13:19 just keep those around unchanged 14:13:48 even process_bugs they are using a copy 14:13:50 that shouldn't be an issue 14:13:54 so yeah 14:13:58 all clear 14:13:59 we can put off housekeeping until the end of the cycle 14:14:07 or whenever kilo is EOL, I guess 14:14:16 k 14:14:20 #info dhellmann to work on migration to releases.o.o 14:14:35 I started a new spec for this, since it involves several steps 14:14:47 #link infra spec: https://review.openstack.org/266506 Move docs.openstack.org/releases to releases.openstack.org 14:14:48 #link https://review.openstack.org/266510 add new vhost for releases.openstack.org 14:14:48 #link https://review.openstack.org/266515 publish from openstack/releases to releases.openstack.org 14:15:08 I've put the spec on the agenda for next week's infra meeting to get it approved 14:15:52 #info ttx to follow-up on consistency checks for release models done 14:16:09 there was the mailing list thread 14:16:10 #link http://lists.openstack.org/pipermail/openstack-dev/2016-January/083726.html 14:16:27 and I just added a follow-up to my countdown thread for this week to mention it again 14:16:46 on to new business 14:16:48 we are still waiting for Magnum 14:17:20 ok, I'll make a note of that in the tagging section of next week's notes 14:17:22 I sent the email personally to Adrian but that didn't really trigger something 14:17:44 Will probably chase him down next week 14:17:59 we can block their tag, if nothing else 14:18:17 I still want to go through the file to check for obvious issues that need fixing 14:18:19 do you have notes about what specifically they need to change? 14:18:26 will do that next week as well 14:18:55 dhellmann: they should switch to cycle-with intermediary 14:19:11 ok 14:19:22 noted under "tagging M2" for next week 14:19:24 since they claim to have a liberty release (but they really haven't) 14:19:38 they need to fix that for mitaka 14:19:57 ok 14:20:07 everyone else that I flagged did their homework 14:20:58 good 14:21:02 so, on to new business 14:21:05 #topic tagging M2 14:21:31 for M1 we had some preparations to do, but I think we're basically set for M2 with tools 14:21:43 is there anything else we need to do before we start accepting M2 tags? 14:21:48 we have one from designate, I think, already 14:22:28 dhellmann: not that I can think of 14:22:45 hello hello 14:22:59 ok, good, that's what I thought, too 14:23:27 #topic open discussion 14:23:35 is there anything else to go over before we end the meeting? 14:24:11 nope 14:24:15 nope 14:24:35 excellent, let's call a short meeting then 14:24:48 #endmeeting