18:01:07 <phrobb> #startmeeting 18:01:07 <odl_meetbot> Meeting started Thu Feb 27 18:01:07 2014 UTC. The chair is phrobb. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:07 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic. 18:01:33 <dmm> #info dmm 18:01:56 <Madhu> #info Madhu for RedHat 18:01:57 <phrobb> #meetingtopic TSC Meeting 2014-02-27 18:02:34 <phrobb> #info Vijoy Pandy present 18:04:03 <phrobb> #topic approval of last week's minutes 18:04:18 <phrobb> #agreed minutes from last week accepted 18:07:56 <RobDolin> #info Rob Dolin, proxy for Rajeev Nagar (Microsoft) 18:08:27 <phrobb> #info question on a group to do interop work and collects and brings back learning 18:09:42 <phrobb> folks, feel free to pound info stuff on this meeting… I have a hard time leading discussions and properly documenting them... 18:09:47 <phrobb> it takes a village :) 18:10:02 * regXboi fighting to get into the webex 18:11:41 <phrobb> regXboi: are you in? 18:11:48 <regXboi> not yet 18:11:56 <phrobb> what's the problem 18:13:51 <RobDolin> #link http://www.isocore.com/mpls2012/ event described by David Meyer 18:14:39 <RobDolin> #info Phil Robb suggests 11 Aug, 2014 as potential release date 18:16:09 <RobDolin> #info David and Vijoy like a time-based approach 18:16:14 <phrobb> #topic Release Date for Helium 18:17:45 <phrobb> #info question/concern brought on avoiding the chaos of code freeze not happening. We need to follow our own process better this time 18:19:44 <phrobb> #info question - if a project misses a milestone, are they off the Helium release? 18:22:04 <chrisprice___> #info Chris Price joined the meeting 18:22:42 <phrobb> #action dmm to kick off a thread to discuss process and rigidity of adherence to release schedule, code freeze, etc 18:22:49 <regXboi> #info regXboi made it in 18:25:24 <phrobb> #info further discussion on release process management ensued 18:27:19 <phrobb> #info comment/concern raised on the amount of code brought into the code base in a recent, short period of time. 18:29:11 <phrobb> #info, comment on getting to and maintaining a solid foundation of code.. is our code base stable/solid enough now or should we have that as a strong focus for Helium? 18:32:35 <phrobb> #info comment on release schedule - Hydrogen should have one or two bug-fix minor releases… this helps with stability… Continued improvement on quality for Helium needs also to be a target 18:33:16 <phrobb> #info comment we need to focus on a better automated integration and testing infrastructure 18:34:27 <phrobb> #info while the integration team and help build out the framework, each project needs to invest in significant improvement in their QA/integration 18:36:22 <phrobb> #info several members express that stable/quality code is essential for user acceptance of OpenDaylight. It needs to be a priority 18:38:14 <phrobb> #info comment on openstack treatment of hypervisors…. class A has had more testing, class B less testing, etc… 18:40:49 <phrobb> #info comments ensued.. plugins cause the aggregate to only be as solid as the weakest link… class designations could work, but the complexity would be difficult 18:41:22 <phrobb> #info this will require more discussion for quality/stability 18:42:05 <phrobb> #info Should we do a "quality based" release schedule instead of a time-based one? 18:42:59 <dbainbri> gonna have to go back and re-take high school chemistry to keep up with the release. 18:47:35 <phrobb> #info discussion continues on time/feature/quality issues for release process 18:51:48 <phrobb> #action dmm and Madhu to write up a proposal on release structure/process for TSC and community review 18:53:05 <phrobb> #info comment made to keep two things in mind… improving process for projects heading to a release is important but improvement of QA/integration infrastructure also needed 18:54:20 <phrobb> #action Carol Sanders to kick off discussion on how to improve QA and integration test suite project activities 18:56:22 <phrobb> #action probb to get an OpenStack rep into TWS call to show automated integration and test infrastructure 19:02:59 <phrobb> #info question, if we use time-base release, can we have criteria available to evaluate a project to drop or keep a project for a simultaneous release? 19:03:13 <phrobb> #info consensus that "yes" that is needed. 19:03:43 <phrobb> #topic Creation Reviews 19:04:08 <phrobb> #info request made for all project proposals schedule creation reviews 19:04:25 <phrobb> #topic DLUX licensing change request 19:05:43 <phrobb> #info comments made that the DLUX project will be sharing code with OpenStack/Horizon more than the rest of the ODP project 19:07:14 <phrobb> #info question what are the unforeseen effects of this, and also, is the problem going to explode with too many licenses 19:12:28 <phrobb> #info comment made that the TSC is evaluating this for technical validity. 19:17:10 <phrobb> #info question to DLUX team on "how much cross project code flow is expected"? 19:17:59 <phrobb> #info once or twice per release cycle is somewhat expect but this is conjecture as we they haven't done it yet. 19:25:50 <phrobb> #agreed TSC has consensus that the technical value of sharing code between horizon and DLUX is valid. 19:26:39 <phrobb> #action probb to set up meeting with IP & Legal for this discussion 19:26:48 <phrobb> #topic TSC at large elections 19:28:18 <phrobb> #action probb to get nominations process moving with a end date of 3/14/2014 19:28:35 <phrobb> #topic Branding discussion 19:29:23 <phrobb> #action probb to set up meeting on branding for when edwarnicke__ is back the week of 23/10/2014 19:29:38 <phrobb> #topic naming / renaming of OVSDB 19:30:04 <phrobb> #action madhu to lead discussion on this at next TSC meeting 19:30:14 <phrobb> #endmeeting