I agree we should release it - and thanks for the link. Per the link the Neon SR3 is December 5 - I think we should keep that schedule (even though there has been a delay on SR2). Since the

You are looking at the wrong release, it is clearly listed here: https://docs.opendaylight.org/en/stable-neon/release-process/release-schedule.html as: Service Release 2 2019-08-08 i.e. we are

Luis, Is your suggestion to pick up the TRNSPRTPCE-126 patch in Neon SR3? BTW I do not see the schedule for Neon SR3 at https://docs.opendaylight.org/en/latest/release-process/release-schedule.html -

OK, lets not wait more time, here is my +1, other TSC members can add to this mail. BR/Luis

Hello, based on the previous, I do not see when the MD-SAL wiring bits will land (but it is on my radar). At some point, this patch (or something equivalent) will have to land in neutron, lest it is

Greetings Robert; I believe any change after the branch is locked requires the TSC vote before anyone from releng can submit/merge the change. Thanks, Anil

Hello, everyone. If you are a developer within the OpenDaylight Project or would like to become one soon, please join us at our next OpenDaylight Developer Forum. This event is by developers for

Thanks. If/when the decision is made on doing a re-spin of Neon SR2, can someone from RelEng just 'Submit' the patch? Regards, Robert

TRNSPRTPCE-126 was only medium priority so it never showed up on our release dashboard when reviewing status of Neon. I just changed it to highest priority. JamO

Hi all TransportPCE has a blocking issue with Neon SR2 that is linked to a bug in our Netconf/restconf upstream dependency and is described in Jira

We still need to move the Mg AR job to jdk11. Please merge https://git.opendaylight.org/gerrit/#/c/releng/builder/+/83642/

Hi TSC, Please find & review the TSC meeting minutes below: https://meetings.opendaylight.org/opendaylight-meeting/2019/tsc/opendaylight-meeting-tsc.2019-08-15-16.00.html If you find something needs

Added to the agenda.

This method would work too _if_ we removed the verify jobs from the job-group. This is because the verify-jobs also use the variable 'java-version' but expects a list instead of a string. In hindsight

Yeah, I meant the URL as a pointer to your explanation :) Hmm... I may be missing something, but wouldn't it suffice if: 1) 'odl-maven-jobs' would *not* define a java-version 2) project definition

This patch won't work because job-groups in JJB do not support defining variables (and variables set in job-groups have the highest priority). The {disable--job} variable that's mistakenly declared in

Multipatch build: https://jenkins.opendaylight.org/releng/job/integration-multipatch-test-sodium/75/ Multipatch+CSIT

I believe so, but we also need an update to job groups for Mg, as currently -merge jobs are running with JDK8, and that has odlparent/master currently broken --

Hello all: As discussed on the integration call today, I'm sending this topic to be included for TSC meeting. We have Autorelease (AR) Sodium with two jobs (openjdk8 and openjdk11) and AR Magnesium

https://wiki.opendaylight.org/view/TSC:Meeting#Agenda