Re: [OpenDaylight Discuss] Allowing integration to have distributions that are not necessarily Release Editions

Luis Gomez

Yes Chris, I believe we can have folder separation between formal and not formal editions if needed, right Ed?


On 4/29/2014 1:12 PM, Chris Wright wrote:
* Ed Warnicke (eaw) (eaw@...) wrote:
The integration project has

Corresponding 1to1 to the Hydrogen Release vehicles of Base Edition,
Virtualization Edition, and Service Provider Edition respectively. Please note that no
decision about the Helium Release Editions have been made yet (and are not expected
until M3 (7/7):

We are starting to see some cross project collaboration activities (like the Karaf stuff)
that would be substantially easier to collaborate on if we could have additional distributions
in the integration project that could take advantage of the integration infrastructure (for example

I don’t think there was ever an explicit decision that integration/distributions/ should *only*
be the Release Editions… but I do know that folks think of it as if there were. And so there was a desire
for some clarification.

What I would suggest is that the TSC make clear that:

1) The integration project committers can decide what things they want in the integration/distributions/
in support of the community doing collaborative integration development (or where ever they decide they should
put distribution like things).
2) The TSC politely requests that the integration project keep distribution directories for each Release Edition in
support of the Release when they are decided.
I could see some value distinguishing Release from less formal (perhaps
just in directory structure) if it helped the docs team monitor the
right spot. If folks think it'ss useful, then that'd be worth
asking for/clarifying as well.

Discuss mailing list

Join to automatically receive all group messages.