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