|
Phosphorus GA release approval
Dear TSC
As you could read from the other email thread, we have can proceed to approve Phosphorus GA release
https://wiki.opendaylight.org/display/ODL/Phosphorus+Formal+Release+Approval
Thanks
Daniel
Dear TSC
As you could read from the other email thread, we have can proceed to approve Phosphorus GA release
https://wiki.opendaylight.org/display/ODL/Phosphorus+Formal+Release+Approval
Thanks
Daniel
|
By
Daniel de la Rosa
·
#13876
·
|
|
Re: [release] [releng][TSC] phosphorus release status - master branch has been locked
Ok. I've sent an email to TSC so the current phosphorus candidate can be approved
Thanks
Ok. I've sent an email to TSC so the current phosphorus candidate can be approved
Thanks
|
By
Daniel de la Rosa
·
#13875
·
|
|
Re: [release] [releng][TSC] phosphorus release status - master branch has been locked
I think netconf devs would be less confused if you could share some writeup of how exactly is test execution wired across integration/test and releng/builder :)
Please note that NETCONF is an MRI
I think netconf devs would be less confused if you could share some writeup of how exactly is test execution wired across integration/test and releng/builder :)
Please note that NETCONF is an MRI
|
By
Robert Varga
·
#13874
·
|
|
Re: [release] [releng][TSC] phosphorus release status - master branch has been locked
I think netconf devs got confused on how our CSIT branches work, I do not see any CSIT job for phosphorous and therefore I do not think we are testing netconf in this
I think netconf devs got confused on how our CSIT branches work, I do not see any CSIT job for phosphorous and therefore I do not think we are testing netconf in this
|
By
Luis Gomez
·
#13873
·
|
|
Re: [release] [releng][TSC] phosphorus release status - master branch has been locked
both #40 and #39 is having this issue
ERROR: Build aborted. Can't trigger undefined projects. 1 of the below project(s) can't be resolved: > netconf-csit-1node-scale-max-devices-only-master
both #40 and #39 is having this issue
ERROR: Build aborted. Can't trigger undefined projects. 1 of the below project(s) can't be resolved: > netconf-csit-1node-scale-max-devices-only-master
|
By
Daniel de la Rosa
·
#13872
·
|
|
Re: [release] [releng][TSC] phosphorus release status - master branch has been locked
So the mri-test-phosphorus does not kick off of autorelease, but runs periodically. I have kicked off #40, but #39 should be accurate.
Regards,
Robert
So the mri-test-phosphorus does not kick off of autorelease, but runs periodically. I have kicked off #40, but #39 should be accurate.
Regards,
Robert
|
By
Robert Varga
·
#13871
·
|
|
Re: [release] [releng][TSC] phosphorus release status - master branch has been locked
Thanks Robert.. I've come up with this phosphorus release approval for TSC
https://wiki.opendaylight.org/display/ODL/Phosphorus+Formal+Release+Approval
but I couldn't find the right mri test ... it
Thanks Robert.. I've come up with this phosphorus release approval for TSC
https://wiki.opendaylight.org/display/ODL/Phosphorus+Formal+Release+Approval
but I couldn't find the right mri test ... it
|
By
Daniel de la Rosa
·
#13870
·
|
|
Re: [release] [releng][TSC] phosphorus release status - master branch has been locked
Okay, so we have one remaining issue in BGPCEP, but after spending today trying to make sense of what is going on, it is not a regression, just shifted timing in code.
It may have been detected
Okay, so we have one remaining issue in BGPCEP, but after spending today trying to make sense of what is going on, it is not a regression, just shifted timing in code.
It may have been detected
|
By
Robert Varga
·
#13869
·
|
|
TSC Meeting for September 30, 2021 at 10 pm Pacific
Hello OpenDaylight Community,
Next TSC meeting is September 30, 2021 at 10 pm Pacific Time.
The agenda proposal and the connection details for this meeting are available at the following
Hello OpenDaylight Community,
Next TSC meeting is September 30, 2021 at 10 pm Pacific Time.
The agenda proposal and the connection details for this meeting are available at the following
|
By
Guillaume Lambert
·
#13868
·
|
|
Re: [release] [releng][TSC] phosphorus release status - master branch has been locked
Okay, I think I found the culprint. A fixed bgpcep should be out in about two hours or so and should be reflect in next AR build.
Bye,
Robert
Okay, I think I found the culprint. A fixed bgpcep should be out in about two hours or so and should be reflect in next AR build.
Bye,
Robert
|
By
Robert Varga
·
#13867
·
|
|
Re: [release] [releng][TSC] phosphorus release status - master branch has been locked
Alright, this looks like a pccmock
Alright, this looks like a pccmock
|
By
Robert Varga
·
#13866
·
|
|
Re: [release] [releng][TSC] phosphorus release status - master branch has been locked
Yeah, it's three test cases, all of them are PCEP-related. They are failing reliably, which seems to indicate a systemic problem.
I'll try to see if I can debug/repro it tomorrow. We might punt to
Yeah, it's three test cases, all of them are PCEP-related. They are failing reliably, which seems to indicate a systemic problem.
I'll try to see if I can debug/repro it tomorrow. We might punt to
|
By
Robert Varga
·
#13865
·
|
|
Re: [release] [releng][TSC] phosphorus release status - master branch has been locked
It seems that we are still having Bgp and pcep issues but are they all critical ? Or can we fix them later so we can release phosphorus ?
It seems that we are still having Bgp and pcep issues but are they all critical ? Or can we fix them later so we can release phosphorus ?
|
By
Daniel de la Rosa
·
#13864
·
|
|
Re: Phosphorus release, input to marketing
I am glad you like it, all MRI projects have been updated to the best of my knowledge.
Ah, yeah, my timing was off last time, joined exactly one hour late :(
Regards,
Robert
I am glad you like it, all MRI projects have been updated to the best of my knowledge.
Ah, yeah, my timing was off last time, joined exactly one hour late :(
Regards,
Robert
|
By
Robert Varga
·
#13863
·
|
|
Re: [releng][TSC] phosphorus release status - master branch has been locked
Hi Robert:
The jjb-merge job failed since a new branch is added and the CR changes a lots of job configs. This translates to updating all the job configs on Jenkins and requires more time to
Hi Robert:
The jjb-merge job failed since a new branch is added and the CR changes a lots of job configs. This translates to updating all the job configs on Jenkins and requires more time to
|
By
Anil Belur
·
#13862
·
|
|
The road to Java 17
Hello everyone,
as you might have noticed, Java 17 has been released: https://jdk.java.net/17/ with reference implementation here: https://jdk.java.net/java-se-ri/17
OpenDaylight currently requires
Hello everyone,
as you might have noticed, Java 17 has been released: https://jdk.java.net/17/ with reference implementation here: https://jdk.java.net/java-se-ri/17
OpenDaylight currently requires
|
By
Robert Varga
·
#13861
·
|
|
Re: Phosphorus release, input to marketing
yes i agree, this does look better than the confluence page ... and I think you meant this page right?
https://docs.opendaylight.org/en/latest/release-notes/projects/controller.html
which looks
yes i agree, this does look better than the confluence page ... and I think you meant this page right?
https://docs.opendaylight.org/en/latest/release-notes/projects/controller.html
which looks
|
By
Daniel de la Rosa
·
#13860
·
|
|
Re: [releng][TSC] phosphorus release status - master branch has been locked
it seems that the issue has been fixed by LF IT so are we good to pick up Phosphorus AR #216 integration #174 is showing some BGPCEP failed test
it seems that the issue has been fixed by LF IT so are we good to pick up Phosphorus AR #216 integration #174 is showing some BGPCEP failed test
|
By
Daniel de la Rosa
·
#13859
·
|
|
Re: Phosphorus release, input to marketing
Hey Daniel,
As I stated before, I do not believe Confluence is the right tool here for long term.
Since we are already maintaining release notes here:
Hey Daniel,
As I stated before, I do not believe Confluence is the right tool here for long term.
Since we are already maintaining release notes here:
|
By
Robert Varga
·
#13858
·
|
|
Re: [releng][TSC] phosphorus release status - master branch has been locked
To explain: it is failing since Sep 21, hence Jenkins jobs do not reflect Gerrit branches mapping:
- all -phosphorus jobs still refer to master branch
- there are no -sulfur jobs
Regards,
Robert
To explain: it is failing since Sep 21, hence Jenkins jobs do not reflect Gerrit branches mapping:
- all -phosphorus jobs still refer to master branch
- there are no -sulfur jobs
Regards,
Robert
|
By
Robert Varga
·
#13857
·
|