16:01:20 <colindixon> #startmeeting MD-SAL Interest call
16:01:20 <odl_meetbot> Meeting started Tue Jun  9 16:01:20 2015 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
16:01:20 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:20 <odl_meetbot> The meeting name has been set to 'md_sal_interest_call'
16:01:25 <colindixon> #topic agenda bashing
16:03:19 <colindixon> #info the main topic today will presumably be bug scrubbing
16:03:45 <colindixon> #link https://lists.opendaylight.org/pipermail/controller-dev/2015-June/009557.html the mail I sent with links to bug scrubbing lists
16:05:59 <colindixon> #info rovarga_ says that during the clustering call there was a call for applications to let them know (and thus also to some extent this call know) what their clustering requirement work
16:07:33 <colindixon> #info catohornet says there were some topics from the past that haven’t been closed: (i) Beryllium planning, (ii) Migration from He to Li (and in the future Li to Be), and (iii) the impact of project spinouts
16:08:58 <colindixon> #topic bug scrubbing
16:10:07 <hideyuki> https://bugs.opendaylight.org/show_bug.cgi?id=3643
16:10:52 <colindixon> #info colindixon asks if we have the links for this in a better place than his e-mail
16:10:59 <colindixon> #info ttkacik says he can play with sharing his bugzilla filters
16:11:30 <colindixon> #info rovarga_ aska bout JIRA progress since it’s easier to share filters there, phrobb says he’s still negotiating if we have a non-commerical license by their rules
16:12:16 <hideyuki> That's the bug VTN project is facing. Please check the bug 3643. (It seems to a bug in yangtools. Since it is MD-SAL call, it is not ok to push a bug of yangtools?)
16:18:27 <colindixon> hideyuki: we’re here
16:18:56 <colindixon> #info ghall_ asks how we figure out when/if to cherry pick things back to Helium
16:20:19 <colindixon> #info ttkacik says we dont have any formal process for this, it’s all ad-hoc
16:22:01 <colindixon> #info ghall_ asks if we want to track which branch things should go to in the scrubbgin, ttkacik says that multi-branch tracking is a lot easer JIRA
16:22:30 <colindixon> #info ghall_ assks what the WAITING_FOR_REVIEW means, rovarga_ it means the the fix is not yet merged, but still in code review
16:23:36 <colindixon> #info colindixon asks if we need a new state NEED_FEEDBACK or NEED_MORE_INFO state
16:24:43 <colindixon> #info rovarga_ and ttkacik say yes and that we should reach out to Andy/Thanh to have it added
16:25:13 <rovarga_> I've seen it called 'information required' somewhere, I think
16:26:49 <colindixon> #action ghall_ to send the request to helpdesk to add the state and help figure out the name if need be
16:27:01 <colindixon> hideyuki: the claim is that the fix is already merged
16:27:03 <rovarga_> #info https://git.opendaylight.org/gerrit/#/c/22189/ for BUG-3643
16:27:09 <rovarga_> #link https://git.opendaylight.org/gerrit/#/c/22189/ for BUG-3643
16:28:24 <hideyuki> (I'm reading the patch and bug 1485.)
16:30:01 <hideyuki> Does it mean the patch (Gerrit/22189) fix the bug 3643?
16:40:47 <colindixon> hideyuki: that’s the claim
16:41:52 <colindixon> #action phrobb to track topics for the design summit, in this case clustering requirements for apps
16:48:59 <hideyuki> colindixon: Ok, we also check if the patch fix the our problem.
16:52:56 <colindixon> #topic Beryllium planning
16:54:14 <colindixon> #info colindixon asks where Beryllium planning is happening? ghall_ asks about maybe using the deisgn summit
16:55:16 <colindixon> #action colindixon to work on pushing the M2 deadline out past the design summit to allow for the design summit input into release plans
16:56:45 <colindixon> #link http://bit.ly/1JCoKaa ttkacik and rovarga_ say that current Beryllium planning is happening on the bug lists with appropriate target milestones
16:57:28 <colindixon> #info ghall_ asks if we have a way to collect project input and aggregate it into requirements and planning? e.g., is this the right meeting for that?
16:58:38 <colindixon> #info colindixon and ttkacik say that this call is the right venue for discussion (once the release is out), but untilmately they want to track things with bugs
16:58:53 <colindixon> #topic He to Li and Li to Be migration
17:00:15 <colindixon> #info Li to Be will obviously be a Beryllium feature if we do it?
17:00:37 <colindixon> #info so far, it looks like He to Li will haveen in an Lithium SR if it happens
17:01:30 <colindixon> #info rovarga_ says we desperately need somebody to drive this to complete and he unfortunately cannot be the person to volunteer for that
17:02:12 <colindixon> #link https://bugs.opendaylight.org/show_bug.cgi?id=3160 this is the bug tracking He to Li upgrades
17:02:16 <colindixon> #topic the scope of this meeting
17:02:30 <colindixon> #info colindixon thinks this meeting will continue to cover the new spinouts, others seem to agree
17:04:31 <colindixon> #info colindixon says that the only other thing, would be maybe trying to fold basic AAA features into this call as well to cover all of the OpenDaylight “core platform"
17:04:38 <colindixon> #action colindixon to try to get more people to attend
17:04:52 <colindixon> #endmeeting