22:02:46 #startmeeting horizon 22:02:46 Meeting started Tue Feb 19 22:02:46 2013 UTC. The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot. 22:02:48 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 22:02:50 The meeting name has been set to 'horizon' 22:03:03 I'm gonna keep this as short as possible 'cuz I'm distracted currently 22:03:08 #General 22:03:11 #topic General 22:03:28 Phenomenal work everyone for all the code and reviews in the last two weeks 22:03:32 seriously, great work 22:03:39 we totally made it 22:03:59 now the important thing is to test test test and find/fix bugs 22:04:09 #topic blueprints and bugs 22:04:31 The only open blueprint is the Quantum LBaaS one, and that's dependent on Quantum getting their FFE 22:04:38 so... we'll just sit on that one. 22:04:50 Bug-wise, I've pared the list in G3 down to things that have assignees 22:05:04 I'll roll them forward to RC1 if they're not done in the next day or two 22:05:32 Anything you find from here on should go into the RC1 milestone. The goal is to identify release-blocking bugs. 22:06:19 Currently the only one I see as blocking is https://bugs.launchpad.net/horizon/+bug/1129190 because they were identified as needed improvements on the review for the blueprint 22:06:21 Launchpad bug 1129190 in horizon "some improvement for network-topology pane" [High,Confirmed] 22:06:32 but I'm sure we'll discover more important bugs as we get into the testing phase 22:06:46 so it's important to keep a close eye on the bug list 22:06:56 that's about all I have. 22:06:59 #topic discussion 22:07:04 I open the floor to everyone else 22:07:27 Are "regular" non-blocker bugs still ok to focus on for fixing, or less important? I'm a bit confused with the different dates (I thought today was code freeze for everything) 22:08:13 absolutely okay 22:08:22 today is code freeze for features 22:08:26 well, actually tomorrow now 22:08:31 there's been a global +1 day 22:08:57 bugfixes can go in as long as we're rolling RC candidates, but the bar gets higher with each successive RC 22:09:07 so in RC1 we can fix anything we feel needs fixing 22:09:12 if we do an RC2 it has to be urgent stuff 22:09:24 if (heaven forbid) there's an RC3 it's only critical show-stoppers 22:09:28 you get the idea 22:09:42 don't count on there being more than an RC1 22:09:52 Ok, cool! RC1 is March 14th, is it? https://wiki.openstack.org/wiki/GrizzlyReleaseSchedule 22:09:58 * jpich trying to read this right this time 22:10:12 I think that's correct 22:10:16 seems like a long time, but yeah 22:10:27 Cheers :) 22:13:46 great 22:13:48 okay 22:13:53 anything else from anybody? 22:14:14 cool! 22:14:21 thanks everyone, same time next week 22:14:24 #endmeeting