|
Re: [documentation] RTD Job - automation rule to activate branch/tag
Yeah, I do not see daexim stable/phosphorus docs for example: https://docs.opendaylight.org/projects/daexim/en/latest/, so it did not work, at least fully :(
Can you please make sure at least these
Yeah, I do not see daexim stable/phosphorus docs for example: https://docs.opendaylight.org/projects/daexim/en/latest/, so it did not work, at least fully :(
Can you please make sure at least these
|
By
Luis Gomez
·
#14037
·
|
|
Re: [documentation] RTD Job - automation rule to activate branch/tag
Greetings Luis:
I've run the script to activate all the projects. Please check and let me know if all the versions are active.
Regards,
Anil
Greetings Luis:
I've run the script to activate all the projects. Please check and let me know if all the versions are active.
Regards,
Anil
|
By
Anil Belur
·
#14036
·
|
|
Re: Phosphorus SR2 code freeze
We're *almost* there, except the ODLPARENT-279 issue, plus BGPCEP integration also found https://jira.opendaylight.org/browse/MDSAL-718.
Both should take a few days to clear.
REgards,
Robert
We're *almost* there, except the ODLPARENT-279 issue, plus BGPCEP integration also found https://jira.opendaylight.org/browse/MDSAL-718.
Both should take a few days to clear.
REgards,
Robert
|
By
Robert Varga
·
#14035
·
|
|
Re: Log4Shell impacts on ODL releases
https://jira.opendaylight.org/browse/ODLPARENT-279 tracks this. It is also affecting Phosphorus SR2 (but that also has a different problem).
Regards,
Robert
https://jira.opendaylight.org/browse/ODLPARENT-279 tracks this. It is also affecting Phosphorus SR2 (but that also has a different problem).
Regards,
Robert
|
By
Robert Varga
·
#14034
·
|
|
Re: [documentation] RTD Job - automation rule to activate branch/tag
Hi Anil,
Is there anyone in ODL with admin permissions on all the RTD projects? If so, can this person generate a token and run this script to activate the stable-phosphorus branch on all the
Hi Anil,
Is there anyone in ODL with admin permissions on all the RTD projects? If so, can this person generate a token and run this script to activate the stable-phosphorus branch on all the
|
By
Luis Gomez
·
#14033
·
|
|
Re: RTD Job - automation rule to activate branch/tag
Hi Anil,
Thanks for pointing this out. I have been meaning to spend some time updating the Unimgr docs, and this is good to know.
BTW, there is an open source themed Hackathon associated with NANOG
Hi Anil,
Thanks for pointing this out. I have been meaning to spend some time updating the Unimgr docs, and this is good to know.
BTW, there is an open source themed Hackathon associated with NANOG
|
By
Charles Eckel <eckelcu@...>
·
#14032
·
|
|
Re: Log4Shell impacts on ODL releases
So pretty much everything is actually okay, except BGPCEP, which is showing regressions around TCP-MD5 handling. This is most probably related to netty-4.1.72+ upgrade in OSGi
So pretty much everything is actually okay, except BGPCEP, which is showing regressions around TCP-MD5 handling. This is most probably related to netty-4.1.72+ upgrade in OSGi
|
By
Robert Varga
·
#14031
·
|
|
Re: [E] Re: [OpenDaylight TSC] Log4Shell impacts on ODL releases
Hello Manoj, Robert and all
As suggested, this is a proposed schedule to release Silicon SR4. It's a bit accelerated but I think we can make it
Hello Manoj, Robert and all
As suggested, this is a proposed schedule to release Silicon SR4. It's a bit accelerated but I think we can make it
|
By
Daniel de la Rosa
·
#14030
·
|
|
Re: [E] [OpenDaylight TSC] TSC Meeting for January 20, 2022 at 10 pm Pacific
Hi All,
I won't be able to attend tonight's call. Sangwook will proxy me.
Regards,
Navid
On Wed, Jan 19, 2022 at 5:54 AM Guillaume Lambert via lists.opendaylight.org
Hi All,
I won't be able to attend tonight's call. Sangwook will proxy me.
Regards,
Navid
On Wed, Jan 19, 2022 at 5:54 AM Guillaume Lambert via lists.opendaylight.org
|
By
Ghazisaidi, Navid
·
#14029
·
|
|
Re: [E] Re: [OpenDaylight TSC] Log4Shell impacts on ODL releases
Hi Daniel,
Since the changes are already done, could you prioritize silicon-SR4 first and then others.
Thank you,
BR, Manoj
Hi Daniel,
Since the changes are already done, could you prioritize silicon-SR4 first and then others.
Thank you,
BR, Manoj
|
By
Chokka, Manoj
·
#14028
·
|
|
Re: Log4Shell impacts on ODL releases
Hey Daniel,
Actually, these updates are already pushed out on the branch, i.e. https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-silicon-mvn35-openjdk11/537/ should be
Hey Daniel,
Actually, these updates are already pushed out on the branch, i.e. https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-silicon-mvn35-openjdk11/537/ should be
|
By
Robert Varga
·
#14027
·
|
|
Re: Phosphorus SR2 code freeze
Hello Daniel,
Unfortunately I am still waiting for last round of updates for CONTROLLER-2025 to push out the MRI update. I expect this to happen this week.
Sorry for the delay,
Robert
Hello Daniel,
Unfortunately I am still waiting for last round of updates for CONTROLLER-2025 to push out the MRI update. I expect this to happen this week.
Sorry for the delay,
Robert
|
By
Robert Varga
·
#14026
·
|
|
Re: Log4Shell impacts on ODL releases
Hello Robert
We can review this in the TSC but I think we can release Silicon SR4 after Phosphorus SR2 and before Sulfur. Thoughts?
Hello Robert
We can review this in the TSC but I think we can release Silicon SR4 after Phosphorus SR2 and before Sulfur. Thoughts?
|
By
Daniel de la Rosa
·
#14025
·
|
|
Re: Phosphorus SR2 code freeze
Hello all
@Robert Varga i think we can pick a Phosphorus SR2 RC this week but let me know your thoughts based on the current AR
Hello all
@Robert Varga i think we can pick a Phosphorus SR2 RC this week but let me know your thoughts based on the current AR
|
By
Daniel de la Rosa
·
#14024
·
|
|
TSC Meeting for January 20, 2022 at 10 pm Pacific
Hello OpenDaylight Community,
The next TSC meeting is January 20 , 2022 at 10 pm Pacific Time.
As usual, the agenda proposal and the connection details for this meeting are available in the wiki
at
Hello OpenDaylight Community,
The next TSC meeting is January 20 , 2022 at 10 pm Pacific Time.
As usual, the agenda proposal and the connection details for this meeting are available in the wiki
at
|
By
Guillaume Lambert
·
#14023
·
|
|
RTD Job - automation rule to activate branch/tag
Hi all,
As discussed on the LFN Dev and testing forums, some of the RTD branches were not activated by default therefore the docs were not getting created. This can be solved by using Automation
Hi all,
As discussed on the LFN Dev and testing forums, some of the RTD branches were not activated by default therefore the docs were not getting created. This can be solved by using Automation
|
By
Anil Belur
·
#14022
·
|
|
Re: Unscheduled Silicon SR4 release
Hello Robert and all. Sure but next tsc meeting is on January 20th. Hopefully this can wait until then
Thanks
--
Daniel de la Rosa
ODL Release Manager
Hello Robert and all. Sure but next tsc meeting is on January 20th. Hopefully this can wait until then
Thanks
--
Daniel de la Rosa
ODL Release Manager
|
By
Daniel de la Rosa
·
#14021
·
|
|
Phosphorus SR2 code freeze
Hello TSC and all
We are going to code freeze Phosphorus for all Managed Projects ( cut and lock release branches ) on Monday January 17th at 10 am pst
Please remember that we only allow blocker bug
Hello TSC and all
We are going to code freeze Phosphorus for all Managed Projects ( cut and lock release branches ) on Monday January 17th at 10 am pst
Please remember that we only allow blocker bug
|
By
Daniel de la Rosa
·
#14020
·
|
|
Unscheduled Silicon SR4 release
Hello everyone,
as per my previous email, we need to spin an unscheduled security-driven Service Release on the Silicon release train.
The MRI part of this is already done and the projects are ready
Hello everyone,
as per my previous email, we need to spin an unscheduled security-driven Service Release on the Silicon release train.
The MRI part of this is already done and the projects are ready
|
By
Robert Varga
·
#14019
·
|
|
Log4Shell impacts on ODL releases
Hello everyone,
these winter holidays we got a present in the form of Log4Shell, which affects pretty much all artifacts we have ever released.
As per our release lifecycle rules, this means
Hello everyone,
these winter holidays we got a present in the form of Log4Shell, which affects pretty much all artifacts we have ever released.
As per our release lifecycle rules, this means
|
By
Robert Varga
·
#14018
·
|