Thank you for the explanation :) +1 for flexibility… at one point I recall the AAA component being swappable at binary level (ie, you just plugged in a different implementation). If that’s no longer t

Tom, I think that may be a good idea… any thoughts on what that mix would look like? Ed

Andy, Chris, I’ve extended Andy’s odlforge etherpad here: https://pad.opendaylight.org/p/odlforge By adding at the top a set of questions that need to be answered for us to proceed on odlforge in an o

So… my initial gut reaction about a hackfest around M3 and M5 is positive… but it might be helpful to think about the reasoning there… To my mind, the reasons for hackfests might be something like thi

Daniel, Thank you for taking a swag at this :) Overall I like your structure very much, but do have a question about the use of the ‘:’ Is such a ‘:’ use the convention in docker-land? Does it convert

:) Ed

Would it make sense (or be possible) to have a Hackfest for Release Planning to 1/13-15 in Santa Clara? The idea would be to get folks together for inter project collaboration on Release Plans (and ho

I think the net-net is this: M1 bumps back 2 weeks (+1 week for holidays for a total of 3… but we are eating the holiday offsets no matter what, so only effectively 2 weeks) Final Lithium Release bump

As part of the ongoing cleanup on controller, there is a patch: https://git.opendaylight.org/gerrit/#/c/12512/ to remove the legacy hydrogen-style distribution. This is in keeping with the integration

Colin, Per the discussion about leaving adequate time M0->M1 and M1->M2, I wanted to throw out some concrete date proposals. I think you’ve expressed agreement that M0 should start from roughly when w

Actually, karaf in Helium is the *perfect* example of why KDC is crucial. We *rushed* the Helium Simultaneous Release Plan out the door. We did *not* KDC karaf for Helium. We *did* make a series of co

I feel kind of strongly that we have at least a Milestone for projects to work out what they need for M1 (particularly planning). The simplest way to do that is M0, but we could figure something else

Comments inline… with some snipping where I think we are violently agreeing ;) I would suggest that if we can’t KDC it prior to approval of the SR, we shouldn’t require it. Now that you say it that wa

Luis, We haven’t crossed M0 yet, because the SR plan has not been approved by the TSC. I am fundamentally opposed to approving a plan with Milestone dates in the past at time of approval. Ed

General Comments: OMG this is so much improved over Helium/Hydrogen :) Principles to Consider: I would suggest that we consider the following principles in looking at the Simultaneous Release Plan: 1)

So… let me ask this question… can we actually realistically carry out this distinction before we have the necessary tooling in hand? Ed

I was thinking something similar, and concur. To my ear, a legacy API is something we expect to be deprecating sooner or later (other ears may disagree ;) ). So I second renaming Legacy API to Stable

I hereby declare my intent to run for a Committer-at-Large seat on the board. https://wiki.opendaylight.org/view/Committer_Board_Members:2014_Election#Ed_Warnicke Most folks know me from my broad invo

I would like to designate Keith Burns (alagalah) as my delegate on the TSC until I return. Many thanks, Ed

+1 Ed