|
Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status
Hello Daniel,
I believe that we can reasonably consider that TransportPCE will not be able to integrate the GA distribution of Sulfur. We could not complete the project migration due to many
Hello Daniel,
I believe that we can reasonably consider that TransportPCE will not be able to integrate the GA distribution of Sulfur. We could not complete the project migration due to many
|
By
Gilles Thouenon
·
#14155
·
|
|
Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status
Hi Daniel
I let Gilles answer the question since he is in charge of this TPCE release.
We can put that at the TSC agenda tomorrow.
BR
Guillaume
De : Daniel de la Rosa <ddelarosa0707@...>
Hi Daniel
I let Gilles answer the question since he is in charge of this TPCE release.
We can put that at the TSC agenda tomorrow.
BR
Guillaume
De : Daniel de la Rosa <ddelarosa0707@...>
|
By
Guillaume Lambert
·
#14154
·
|
|
Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status
Thanks Anil .. So @LAMBERT Guillaume TGI/OLN are you going to skip Sulfur to TPCE? I can start with Sulfur SR1 code freeze as scheduled next week while Sulfur GA is getting ready
Thanks Anil .. So @LAMBERT Guillaume TGI/OLN are you going to skip Sulfur to TPCE? I can start with Sulfur SR1 code freeze as scheduled next week while Sulfur GA is getting ready
|
By
Daniel de la Rosa
·
#14153
·
|
|
TSC Meeting for May 5, 2022 at 9 am Pacific
Hello OpenDaylight Community,
The next TSC meeting is May 5, 2022 at 9 am Pacific Time.
As usual, the agenda proposal and the connection details for this meeting are available in the wiki
at the
Hello OpenDaylight Community,
The next TSC meeting is May 5, 2022 at 9 am Pacific Time.
As usual, the agenda proposal and the connection details for this meeting are available in the wiki
at the
|
By
Guillaume Lambert
·
#14152
·
|
|
Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status
+tsc
By
Anil Belur
·
#14151
·
|
|
TSC Meeting for April 28, 2022 at 10 pm Pacific
Hello OpenDaylight Community,
The next TSC meeting is April 28, 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 April 28, 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
·
#14150
·
|
|
Re: [E] Re: [OpenDaylight TSC] [release] Sulfur code freeze
OFP clustering is not very stable yet but I'm okay with addressing it later with SR1.
Thanks,
Sangwook
OFP clustering is not very stable yet but I'm okay with addressing it later with SR1.
Thanks,
Sangwook
|
By
Sangwook Ha
·
#14149
·
|
|
TSC approval of Sulfur GA
Hello TSC
Please approve Sulfur AR #30 as RC for Sulfur GA as soon as possible
https://wiki.opendaylight.org/display/ODL/Sulfur+Formal+Release+Approval
Thanks
--
Daniel de la Rosa
ODL Release Manager
Hello TSC
Please approve Sulfur AR #30 as RC for Sulfur GA as soon as possible
https://wiki.opendaylight.org/display/ODL/Sulfur+Formal+Release+Approval
Thanks
--
Daniel de la Rosa
ODL Release Manager
|
By
Daniel de la Rosa
·
#14148
·
|
|
Re: [release] Sulfur code freeze
ok @Ha, Sangwook and all TSC, if you are ok with releasing Sulfur in its current state, AR#30 and integration #220, please approve it at
ok @Ha, Sangwook and all TSC, if you are ok with releasing Sulfur in its current state, AR#30 and integration #220, please approve it at
|
By
Daniel de la Rosa
·
#14147
·
|
|
MRI projects in churn
Hey everyone, especially those working on ODL
We are currently transitioning to JDK17 as part of Chlorine MRI bump.
Unfortunately we are at this point 11 days past the deadline, so things are moving
Hey everyone, especially those working on ODL
We are currently transitioning to JDK17 as part of Chlorine MRI bump.
Unfortunately we are at this point 11 days past the deadline, so things are moving
|
By
Robert Varga
·
#14146
·
|
|
Re: [release] Sulfur code freeze
So we have latest AR here: https://jenkins.opendaylight.org/releng/job/autorelease-release-sulfur-mvn38-openjdk11/29/
Triggered by Sangwook, because the previous run failed. We can expect AR #30 in
So we have latest AR here: https://jenkins.opendaylight.org/releng/job/autorelease-release-sulfur-mvn38-openjdk11/29/
Triggered by Sangwook, because the previous run failed. We can expect AR #30 in
|
By
Robert Varga
·
#14145
·
|
|
Re: Old RESTCONF northbound scheduled for removal
[snip]
The old implementation is no longer present in netconf/master, hence this item is slated for delivery in 2022.09 Chlorine.
Regards,
Robert
[snip]
The old implementation is no longer present in netconf/master, hence this item is slated for delivery in 2022.09 Chlorine.
Regards,
Robert
|
By
Robert Varga
·
#14144
·
|
|
Re: The road to Java 17
Hello again,
[snip]
These issues have been addressed.
Both these items are delivered, all projects participating on Sulfur GA verify each patch with both JDK11 and JDK17.
This is now slated for
Hello again,
[snip]
These issues have been addressed.
Both these items are delivered, all projects participating on Sulfur GA verify each patch with both JDK11 and JDK17.
This is now slated for
|
By
Robert Varga
·
#14143
·
|
|
Re: [release] Switching default build node to centos8-builder-4c-4g
Hmm, that would be a major problem and really soon. Sigul is part of stage jobs -- stage i.e. build + sign. We are exactly 2 patches away from odlparent/master requiring JDK17 to build -- and that
Hmm, that would be a major problem and really soon. Sigul is part of stage jobs -- stage i.e. build + sign. We are exactly 2 patches away from odlparent/master requiring JDK17 to build -- and that
|
By
Robert Varga
·
#14142
·
|
|
Re: [release] Switching default build node to centos8-builder-4c-4g
+1 We should be able switch to CentOS8 for the jobs that require JDK17, but there could be a few caveats that we should consider before we move the rest of the builders nodes.
Sigul (artifact
+1 We should be able switch to CentOS8 for the jobs that require JDK17, but there could be a few caveats that we should consider before we move the rest of the builders nodes.
Sigul (artifact
|
By
Anil Belur
·
#14141
·
|
|
Re: [release] [OpenDaylight TSC] Switching default build node to centos8-builder-4c-4g
+1
Od: release@... <release@...> v mene používateľa Luis Gomez <ecelgp@...>
Odoslané: piatok, 22. apríla 2022 1:57:03
Komu: Robert Varga
Kópia: infrastructure@...; release@...;
+1
Od: release@... <release@...> v mene používateľa Luis Gomez <ecelgp@...>
Odoslané: piatok, 22. apríla 2022 1:57:03
Komu: Robert Varga
Kópia: infrastructure@...; release@...;
|
By
Ivan Hrasko
·
#14140
·
|
|
Re: Switching default build node to centos8-builder-4c-4g
LGTM, any change for updating current infra is +1 for me :)
LGTM, any change for updating current infra is +1 for me :)
|
By
Luis Gomez
·
#14139
·
|
|
Re: [integration-dev] [releng][TSC] Sulfur release status - master branch has been locked
Hello all,
The version bump is complete, the master branch is promoted to the next release (Chlorine) and the "stable/sulfur" branch has been created.
Note: The master branch (Chlorine) is unlocked
Hello all,
The version bump is complete, the master branch is promoted to the next release (Chlorine) and the "stable/sulfur" branch has been created.
Note: The master branch (Chlorine) is unlocked
|
By
Anil Belur
·
#14138
·
|
|
[integration-dev] [releng][TSC] Sulfur release status - master branch has been locked
Hello all,
The master branch is locked for Sulfur code freeze and branch cutting ("stable/sulfur") and master branch will be promoted to next (Chlorine), which will be the development version. Once
Hello all,
The master branch is locked for Sulfur code freeze and branch cutting ("stable/sulfur") and master branch will be promoted to next (Chlorine), which will be the development version. Once
|
By
Anil Belur
·
#14137
·
|
|
Switching default build node to centos8-builder-4c-4g
Hello everyone,
we are currently defaulting to centos7-builder-4c-4g here: https://github.com/opendaylight/releng-builder/blob/master/jjb/defaults.yaml#L19=
CentOS7 is ancient and cannot support our
Hello everyone,
we are currently defaulting to centos7-builder-4c-4g here: https://github.com/opendaylight/releng-builder/blob/master/jjb/defaults.yaml#L19=
CentOS7 is ancient and cannot support our
|
By
Robert Varga
·
#14136
·
|