[OpenDaylight TSC] [release] [OpenDaylight Discuss] Boron planning

Jamo Luhrsen jluhrsen at gmail.com
Thu Mar 3 02:03:13 UTC 2016

On 03/02/2016 05:56 PM, Colin Dixon wrote:
> If I remember correctly, you made the argument (which I think I agree with) that we probably didn't need to adjust the
> release plan to get more testing earlier, but instead actually enforce the milestones we already have in the release to
> encourage more discipline from projects.

The integration/test project does want to ask for two more requirements, but I'm
not sure the right process to get it in the release plan (just go write it down
in the wiki and advertise to release list?)

1) https://wiki.opendaylight.org/view/Integration/Test/Test_Case_Expectations

2) each project's top level features start with "experimental" state, and are
promoted out of that state during release review based on any number of factors,
but at least based on their delivery of system test.

This can to either FFB or our historical 6month release plans.


> --Colin
> On Mar 2, 2016 4:39 PM, "Colin Dixon" <colin at colindixon.com <mailto:colin at colindixon.com>> wrote:
>> Inline.
>> On Wed, Mar 2, 2016 at 3:26 PM, Robert Varga <nite at hq.sk <mailto:nite at hq.sk>> wrote:
>>> On 03/02/2016 02:08 PM, Colin Dixon wrote:
>>>> For better or for worse, we're at a point where if we don't approve a Boron release plan soon—really this
> Thursday—we risk delaying the Boron release by likely a month or more as it will cross over the OpenDaylight summit.
>>> So that would be tomorrow. It does feel a bit hurried -- even though this is a copy&paste of the familiar thing, I
> would prefer us to have a week of buffer, especially because the current version does not include things that we talked
> about: notably moving requirements testing by one milestone sooner, so we do not get into the RC0 churn we did in Be.
> _______________________________________________
> release mailing list
> release at lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/release

More information about the TSC mailing list