15:01:12 <ttx> #startmeeting releaseteam
15:01:13 <openstack> Meeting started Fri Mar 31 15:01:12 2017 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:17 <openstack> The meeting name has been set to 'releaseteam'
15:01:41 <ttx> Agenda on R-22 at https://etherpad.openstack.org/p/pike-relmgt-tracking
15:01:51 <dims> o/
15:02:02 <ttx> #topic Current status
15:02:24 <ttx> I'm still catching up from my travel week
15:02:30 <ttx> dims: anything to mention ?
15:02:41 <lbragstad> o/
15:02:48 <dims> ttx : pretty quiet week, no fires
15:02:54 <ttx> great!
15:02:56 <dhellmann> I'm also catching up after being offline
15:03:07 <ttx> dims: so nothing requiring our urgent attention
15:03:16 <dims> we could use eyes on stable releases..
15:03:17 <ttx> I deferred reviews due to infra issues
15:03:22 <dhellmann> I'm currently going through the open reviews and rechecking the ones where the logs are missing so we can review them next week
15:04:22 <fungi> yes, please hold off approving releases until we clear the alert for the static server. you might wind up with thigs like the pypi upload job failing to retrieve a tarball
15:04:24 <ttx> Ok
15:04:24 <dhellmann> that assumes all of those 404 errors are really related to files being missing, I guess
15:04:52 <ttx> Pike-1 is just around the corner, we completed most actions
15:05:02 <ttx> "I need more detail about what the TC resolution for releases.o.o should say"
15:05:16 <ttx> We have plenty of things in the backlog, so wouldn't mind if we pushed that during p-2
15:05:30 <ttx> (TC backlog)
15:05:33 <fungi> dhellmann: right now we're not serving the logs.o.o site normally, so i wouldn't take current inability to find logs as an indication they're really gone until we get the filesystem situation cleared up
15:05:40 <ttx> I don't feel like it's P-1-urgent
15:05:45 <dhellmann> fungi : ah, ok, I'll stop rechecking
15:06:02 <dhellmann> ttx: wfm.
15:06:08 <ttx> moving it to p2
15:06:26 <fungi> the log renderer in particular eats a ton of memory and we need every bit of that for the fsck on the logs volume so have disabled the logs.o.o apache vhost
15:06:50 <ttx> #topic Priority reviews
15:07:07 <ttx> Only one holding up a P-1 item would be https://review.openstack.org/#/c/448173/
15:07:43 <ttx> so I think we are good
15:07:46 <ttx> anything else ?
15:08:02 <dhellmann> not from me
15:08:26 <ttx> #topic Move meeting to 1400 utc ?
15:08:31 <ttx> I know fungi won't like this one
15:08:52 <fungi> meh
15:09:00 <ttx> In past cycles we adjusted the summer meeting time so that it's earlier in the day for me
15:09:02 <fungi> i can edit my reminder
15:09:09 <ttx> Given that most of the meetings are under 30 min, I don't care taht much
15:09:21 <dhellmann> I'm fine either way
15:09:25 <ttx> so let me know if you'd rather change or keep it
15:09:48 <ttx> If we can keep the meetings under 30min that doesn't push too much into critical end of day space
15:10:52 <ttx> Oh well, let's keep it where it is until it becomes more of a problem
15:11:08 <fungi> wfm
15:11:36 <dhellmann> shorter meetings are also good, so that's fine
15:11:47 <ttx> We could technically get rid of the meeting and try to go fully async
15:12:02 <ttx> but I'll let the SWG experiment with that first
15:12:20 <dhellmann> that might be interesting to try, too
15:12:22 <dhellmann> but yeah
15:12:30 <ttx> the meeting used to be the focal point to contact us, but those days people know the channel
15:12:47 <dhellmann> true
15:13:36 <ttx> Another thing I wanted to mention: whenever you think of something we should mention in the weekly countdown email, please add it to the corresponding week on the tracing page
15:13:44 <ttx> tracking*
15:13:58 <ttx> as sometimes it's a bit dry
15:14:18 <dhellmann> sure. the process doc has some reminders for different points through the cycle, but I assume you've pulled those in already?
15:14:46 <ttx> dhellmann: yes, for up to pike-1. I'll lay down the point for Pike-2 period once we hit that
15:14:54 <ttx> points*
15:15:02 <dhellmann> yeah, I always tried to keep those minimal with clear instructions, so I'm sure they were not riveting reading
15:15:08 <dhellmann> ++
15:15:09 <ttx> agile sprints and all
15:15:30 <ttx> alright, let's close early again
15:15:36 <ttx> Have a great weekend!
15:15:43 <ttx> #endmeeting