18:01:47 <SlickNik> #startmeeting trove
18:01:48 <openstack> Meeting started Wed Apr  8 18:01:47 2015 UTC and is due to finish in 60 minutes.  The chair is SlickNik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:01:49 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:01:52 <openstack> The meeting name has been set to 'trove'
18:02:07 <amrith> ./
18:02:14 <sushilkm> hello all
18:02:23 <georgelorch> o/
18:02:27 <SlickNik> Giving folks a couple of minutes to trickle in.
18:02:44 <SlickNik> Agenda at:
18:02:48 <SlickNik> #link https://wiki.openstack.org/wiki/Meetings/TroveMeeting#Weekly_Trove_Team_Meeting
18:02:54 <dougshelley66> o/
18:03:33 <SlickNik> Short agenda today — should be a fairly quick meeting.
18:03:37 <atomic77> o/
18:03:47 <SlickNik> #topic Trove pulse update
18:04:03 <SlickNik> #link https://etherpad.openstack.org/p/trove-pulse-update
18:04:10 <peterstac> o/
18:05:12 <SlickNik> Fairly consistent reviews this week as well — around the 1xx mark
18:06:25 <SlickNik> Also — I've been keeping an eye out on the average wait time — It's good to see that coming down across all changes.
18:06:30 <vgnbkr> o/
18:07:10 <SlickNik> (46 -> 24 -> 19 -> 14 days)
18:07:26 <amrith> amen to that!
18:08:06 <SlickNik> I was going to look into trying to get some visualization of this data over time (now that we have more than a few datapoints).
18:08:25 <SlickNik> That would make it easier for us to look at every week — rather than the raw stats.
18:09:22 <SlickNik> Let's move on, if there are no questions.
18:09:41 <SlickNik> .
18:09:45 <SlickNik> #topic Exceptions in Unit Tests
18:09:50 <SlickNik> vgnbkr: around?
18:10:06 <dougshelley66> he just went to grab a coffee - back in one min
18:10:25 <dougshelley66> i suspect he figured agenda item 1 would take longer... :)
18:10:28 <amrith> nice, coffee ...
18:10:47 <vgnbkr> Hi.
18:11:12 <SlickNik> hi vgnbkr
18:11:34 <vgnbkr> Just wanted to propose that we use assertRaisesWithRegexp instead of assertRaises wheneven we are checking errors against generic exceptions like TroveError or RuntimeError.
18:11:36 <vgnbkr> Thought.
18:11:43 <vgnbkr> Thoughts?
18:12:01 <SlickNik> Sounds like a good proposal.
18:12:10 <vgnbkr> Just checking RuntimeError, you could be getting the wrong one.
18:12:52 <SlickNik> Right unless you checked the message in this case, you can't be sure that you're testing for the exact error that you're expecting.
18:13:10 <SlickNik> Since there are multiple code paths that may raise a RuntimeError.
18:13:20 <SlickNik> Sounds reasonable to me.
18:13:38 <amrith> the proposal is to do this moving forward, right?
18:13:45 <amrith> not to do a wholesale sweep
18:14:03 <vgnbkr> Correct.  I don't think it's worth doing a sweep to change what's already there.
18:15:05 <amrith> is this a cleanup for later, a cleanup over time, no benefit to cleaning up?
18:15:57 <vgnbkr> I'd say cleanup over time.  If a changeset affects a test, a reviewer can suggest updating the assertRaises.
18:16:13 <sushilkm> one can do the cleanup also ... why not
18:16:30 <amrith> I would rather not do the cleanup
18:16:42 <amrith> it is not, I believe of sufficient incremental value
18:16:48 <SlickNik> sushilkm: opportunity costs.
18:16:48 <amrith> and merely a lot of code change
18:17:14 <SlickNik> While it's possible that something else might be raising the same exception, and a bug might be lurking - it's also improbable.
18:17:41 <vgnbkr> +1 SlickNik
18:17:45 <SlickNik> Might make sense to focus development time on other pressing issues of higher importance.
18:17:50 <amrith> +1 SlickNik
18:18:08 <sushilkm> okies ... :)
18:18:53 <SlickNik> Okay, looks like most folks are on board with this.
18:19:14 <amrith> on board, +1
18:19:16 <SlickNik> Make it so.
18:19:42 <SlickNik> Let's move on with the agenda.
18:19:59 <SlickNik> #topic Liberty Design Summit sessions
18:20:35 <SlickNik> So ttx sent out an email regarding this recently
18:20:46 <SlickNik> Let me find a link
18:20:49 <SlickNik> #link http://lists.openstack.org/pipermail/openstack-dev/2015-April/060503.html
18:21:53 <SlickNik> I've been working with him, and it looks like in addition to the  3-4 traditional "fishbowl" sessions, we'll also have 4-5 working sessions, and the contributors meetup on Friday.
18:22:42 <SlickNik> I've set up an etherpad where we can brainstorm / discuss topics for the sessions at: https://etherpad.openstack.org/p/trove-liberty-proposed-sessions
18:22:44 <SlickNik> #link https://etherpad.openstack.org/p/trove-liberty-proposed-sessions
18:24:03 <SlickNik> I'm going to add a couple of ideas I had for sessions to that etherpad later today — and I encourage everyone else to do the same.
18:25:06 <dougshelley66> sounds good
18:25:58 <SlickNik> We have some time before we finalize the design summit schedule, so I'd like to kick this off and give us enough time to discuss this before we set the schedule in stone.
18:26:41 <SlickNik> Also gives us the opportunity to figure out which sessions would be better as working sessions vs. fishbowl sessions since we have that distinction this Summit.
18:27:01 <amrith> what is the difference between a fishbowl and a working session?
18:27:30 <amrith> oh, that's the TL;DR
18:27:33 <amrith> never mind
18:27:36 <amrith> IR;IU
18:28:16 <SlickNik> fishbowl session: large room, open discussions, everyone encouraged to attend (including users / operators) and provide feedback.
18:28:44 <SlickNik> working session: sort of like the mid-cycle sprint. Mostly contributors, smaller audience / room.
18:29:11 <SlickNik> Worth making the distinction in case others had that same question.
18:29:56 <SlickNik> Okay, that's all I had on this. Any questions?
18:30:20 <SlickNik> .
18:30:26 <SlickNik> Let's move on.
18:30:33 <SlickNik> #topic Open DIscussion
18:31:16 <SlickNik> Any items for open discussion today?
18:31:41 <SlickNik> .
18:32:08 <SlickNik> Looks like no — so we can end early and give folks some of the time back!
18:32:25 <SlickNik> Oh, just an FYI.
18:32:25 <amrith> thanks SlickNik
18:32:43 <SlickNik> I'm working with ttx to cut the kilo RC this week.
18:33:08 <SlickNik> So if there's a high-pri bug that you come across that should absolutely make it into kilo, please let me know ASAP.
18:33:48 <SlickNik> #endmeeting