15:00:17 #startmeeting manila 15:00:17 Meeting started Thu Mar 19 15:00:17 2015 UTC and is due to finish in 60 minutes. The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:21 Hi 15:00:22 The meeting name has been set to 'manila' 15:00:30 hello all 15:00:31 Hiho 15:00:33 hello 15:00:42 hi 15:01:01 hi 15:01:17 #agenda https://wiki.openstack.org/wiki/Manila/Meetings 15:01:23 hi 15:01:46 #topic K-3 / feature freeze 15:02:16 The K-3 milestone was tagged this morning! 15:02:28 #link http://git.openstack.org/cgit/openstack/manila/tag/?id=2015.1.0b3 15:02:36 ship it! 15:02:39 yay 15:02:48 We got all the targeted BPs completed, and a few bugs too 15:02:59 some bugs got kicked out to RC1 15:03:02 Hi 15:03:09 hi 15:03:14 \o 15:03:20 at this point nobody can merge new features without a feature freeze exception 15:03:42 the procedure for FFEs is to request them on the mail list 15:03:57 but I don't anticipate the need to grant any 15:04:30 so this means that from now until liberty opens up, we're in bugfix mode 15:04:42 also, we should be TESTING! 15:05:06 I want to drive to get all the known bugs fixed ASAP, and then cut a release candidate 15:05:22 everyone is expected to download and test the hell out of the release candidate 15:05:27 that will probably happen in about 2 weeks 15:05:38 maybe 3 if we can't get the bugs down close to zero 15:05:58 o/ - here 15:06:28 it would be nice if our automated test coverage was 100%, but it's not, which is why testing is very important, especially have we have an RC 15:06:44 especially *after 15:07:06 any questions about feature freeze? 15:07:30 are you interested in adding more _unit_ test coverage now? I was assuming that should wait for L to merge. 15:07:35 I'm really happy with how milestone 3 went by the way 15:07:59 everyone got their stuff in fairly early and we got the reivews we needed and the gate didn't cause too many problems 15:08:12 markstur: adding tests is always welcome 15:08:50 with the possible exception of right around the release when we're scared to break anything 15:09:42 so you might see features going into the client, or to the horizon fork after the feature freeze, but that should slow down soon 15:10:01 they're not technically frozen but we want to keep them stable 15:10:24 #topic Core team nominations 15:10:42 so we have a very small core team -- just 3 people currently 15:10:51 it's no secret that I've been wanting to grow it 15:11:18 for example the last 2 days xyang is out of office, and when vponomaryov pushes a change, he can't +2 is own change 15:11:28 which puts us in a bind 15:11:57 I have nominated u_glide to join the core team already (see the ML post) 15:12:23 and I'm looking for more people who are dedicated to the project to nominate too 15:12:37 cool 15:12:57 the primary requirement is a history of quality code reviews, and participation in the community (IRC channel, ML, and meetups) 15:13:10 contributions to manila core also help a lot, but aren't required 15:13:45 so I'll talk to some of you and see if you're interested 15:13:53 bswartz: contributions make influence to reviews, so it is preffered 15:14:27 vponomaryov: I think that's what I said 15:14:48 vponomaryov: yeah, its easier to review once you understand and contribute code 15:15:19 just my $0.02 15:15:21 the point is that the "core team" is primarily defined by our reviewing responsibility 15:15:29 yep 15:15:59 someone can be a big contributor but not spend time on reviews and not be a core reviewer 15:16:14 and that's fine 15:16:35 I'm hoping to get the core team to around 6 people by start of liberty 15:16:48 I think it will help with review load 15:16:54 but only if we find good candidates 15:17:27 #topic open discussion 15:17:39 that's all I have for today 15:17:51 we can breathe a sigh of relief that we reached the milestone 15:18:05 but only a short one because it's time to get on to testing bugfixing 15:18:05 sigh 15:18:08 lol 15:18:18 I have a topic 15:18:27 also K-4 is a good time to work on documentation 15:18:50 lpabon: go ahead 15:18:53 ^ yeah that.. specially for new developers (like me) is really needed 15:18:57 si.. 15:19:00 (short one) 15:19:28 So, I'm starting with the development environment, and hopefully will be adding documentation next week 15:19:49 oh your topic was documentation 15:19:50 I created https://github.com/lpabon/devstack-manila - which creates a vagrant development image 15:19:58 yes, docs are important 15:20:10 so is bug finding/fixing 15:20:11 yeah, my topic is that we need more development documentation, specially how to start up easily 15:20:31 so we can review and verify fixes 15:20:40 I'm sure everyone wants to start prototyping features for liberty, but let's make sure kilo is successful first 15:20:58 Anyways that's all i had 15:21:08 kaisers: did you have something? 15:21:57 kaisers had a short sigh 15:22:02 lol 15:22:05 okay 15:22:15 just a note about me 15:22:23 I will be at disney world next week 15:22:32 yep :) 15:22:37 sweet (i was just there) 15:22:38 I should be able to hold this meeting next week from the orlando airport 15:22:48 but I'll be unavailable most of the week 15:22:56 maybe I can do reviews in the evening for bugfixes 15:23:07 k3 is tagged. I'm going to Disney World! (Ben is doing the MVP thing) 15:23:18 ^ yes 15:23:30 lol 15:23:43 you can catch me online up through Sunday though 15:23:55 reviews from the roller coaster, yay all +/-2 15:24:05 anyways that's all from me 15:24:31 thanks everyone, and get on to testing/fixing! 15:24:42 thanks, have fun & bye 15:24:45 #endmeeting