18:00:50 #startmeeting trove 18:00:52 Meeting started Wed Sep 3 18:00:50 2014 UTC and is due to finish in 60 minutes. The chair is SlickNik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:53 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:55 The meeting name has been set to 'trove' 18:01:02 o/ 18:01:05 Giving folks a few moments to trickle in. 18:01:22 o/ 18:01:23 o/ 18:01:23 o/ 18:01:26 o/ 18:01:28 o/ 18:01:51 o/ 18:02:33 o/ 18:02:51 Agenda at: 18:02:56 #link https://wiki.openstack.org/wiki/Meetings/TroveMeeting 18:03:19 #topic Juno-3 18:03:45 #link https://launchpad.net/trove/+milestone/juno-3 18:03:53 o/ 18:04:19 o/ 18:04:47 Most of the BPs that we were targeting to merge in Juno-3 have been code-reviewed, and approved and are currently making their way through the integrated gate. 18:05:25 Thanks for the hard work that a lot of you guys put in to making this milestone happen! 18:06:38 Still need to watch the patches through the gate and make sure they merge fine — will be keeping an eye out on that today. 18:07:00 The plan is to cut Juno-3 tomorrow once everything that is in flight merges. 18:07:39 There were a couple of BPs that didn't make it in time for Juno-3 18:08:49 #link https://blueprints.launchpad.net/trove/+spec/associate-flavors-datastores 18:08:51 and 18:09:17 #link https://blueprints.launchpad.net/trove/+spec/oslo-messaging 18:10:53 So we're in Feature Freeze after the juno-3 cut - Any BPs to merge after this needs to have a FFE (Feature Freeze Exception) 18:11:17 SlickNik: whats the rule on bugs? 18:11:36 iccha: Bugs can continue to merge up to and until the RC is cut. 18:11:38 One sec 18:11:57 #link https://wiki.openstack.org/wiki/Juno_Release_Schedule 18:12:17 o/ 18:12:34 So the first RC is planned for the week of Sept 25. 18:13:06 SlickNik, are we the only project who didn't adopt oslo messaging yet? 18:13:18 So basically we have from now until that time to fix bugs, add tests, and polish the overall Juno release. 18:14:06 sgotliv: I think so — although I'm planning on asking for an FFE for that (since we're pretty close) and getting that merged within the next week. 18:14:37 look, it too shame :-) 18:14:57 we need start reviewing this 18:15:20 sgotliv: I think it's not ready for reviews yet. There are issues with it passing the tests. 18:15:31 From when I looked at it last. 18:15:46 ^ esp: any updates? 18:15:46 damn 18:15:54 yo 18:16:11 so I’m knee deep in internal work here 18:16:25 have not worked on oslo.messaging in a while 18:16:39 if someone wants to take it up I can tell ya where I left things 18:16:48 esp: got it. 18:16:59 I believe vipul expressed some interest a while back 18:17:05 but I know he’s busy too 18:17:33 sgotliv: Do you have cycles to take this on, since you expressed an interest? 18:17:50 I already regret about it :-) 18:17:58 SlickNik: Is this something we have to get out for Juno? 18:18:07 joke, I'll try to look into it 18:18:27 grapex: yes, I think this is something we need to complete for juno. 18:18:34 sgotliv: let me know if I can help (or confuse you) 18:19:03 of course, I'll start with fpercoco he is my teammate here at red hat 18:19:17 he is a drafter 18:20:03 sgotliv: cool 18:20:16 I can abandon the patch I got up there too 18:20:29 it’s way crusty 18:20:59 sgotliv / esp: I'd check with vipul before doing that, since I know he was looking at it as well. 18:21:13 sure 18:21:29 SlickNik: k, will do 18:21:42 Okay, so coming back to bugs. 18:22:04 We've already identified quite a few issues that we should get fixed in Juno. 18:22:27 We now have an RC1 milestone, so I'm going to move all of these issues that we've identified to this RC1 milestone. 18:23:24 ./ 18:23:37 Will complete that by tomorrow, so folks have a better idea of how RC1 is shaping up. 18:24:10 (and who's looking at which RC1 issues) 18:24:45 Any other questions regarding Juno-3, and the path to RC1? 18:25:35 . 18:25:41 #topic Open Discussion 18:26:16 Any items for Open Discussion? 18:26:42 just reading scrollback 18:26:52 sgotliv, if you want a hand with oslo.messaging, happy to help. 18:27:40 amrith, thanks, I definitely will need a help 18:27:58 SlickNik, I am slowly getting ramped up here and learning many various bits. If you need a body to do things like testing, bug validation, etc...feel free to ping me, would be good exercises to help me get rolling. 18:28:40 georgelorch: Will definitely do. 18:28:58 georgelorch, I have few ideas, ping me tomorrow 18:29:12 georgelorch: Definitely pull down some of the new bits added in juno-3, and test and file bugs if anything seems amiss. 18:29:43 Also in general now would be a good time to start looking at the docs tasks that have been in the queue as well. :) 18:30:16 sure SlickNik, currently working on getting hardware/devstack running in a reasonable environment, code pulled, etc...will jump in... 18:30:21 sgotliv, will do 18:30:45 Anything else for open discussion? 18:30:58 . 18:31:03 #endmeeting