|
Re: [release] Sulfur SR1 and Phosphorus SR3 announcement
Daniel de la Rosa
On Thu, May 19, 2022 at 12:09 PM Robert Varga < nite@...> wrote: On 19/05/2022 17:42, Robert Varga wrote:
>> phosphorus looks ready for SR3. I'm going to pick AR #48 since it
>> looks ready if everybody is ok with that
>>
>> https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/408/
>> <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/408/>
>>
>
> Not quite, there was a snag with netty-4.1.77, hence the MRI bump is not
> complete yet (still needs bgpcep release, which I am in the process of
> spinning). The bump should be ready tomorrow CET.
This is done and should be part of next AR run.
Great, thanks for the update. So I think for phosphorous, we can go with AR#50 even when we had a non critical issue with OFP
For Sulfur SR1, I'll just pick the build 53 since they are all still in the same state..
Any comments before i put these two for approval
Regards,
Robert
|
|
|
Remote Participation at the Porto DTF
Heather Kirksey <hkirksey@...>
Dear Communities, We are getting numerous requests for our June Developer and Testing Forum to be a hybrid event. We understand why: some geographies are still experiencing surges, corporate travel policies remain conservative, and some community members are not yet ready to travel. These are all valid. The answer is, sadly, that we can’t. Bluntly, enabling a hybrid event would incur about a full 30% increase in total cost for what is a free event. We cannot do this and remain fiscally responsible. Additionally, it’s not a great experience for either on-site or remote participants. As Unix philosophy states, “Do one thing and do it well.” Since Unix philosophy also asserts the "need to work together,” LFN staff have come up with some adhoc solutions to enable community participation that will be provided on an unmanaged, self-serve, best effort basis. Please note that last sentence and note it well. We can enable but not ensure remote participation. Here is what it looks like: All devices will be on the same Wifi network, including the presenter/facilitator slide show (i.e., subject to venue Wifi and public internet considerations) – there will be no managed network for presenter laptops.
We cannot guarantee integration into the in-room microphone and A/V set-up. Attendees can obviously use things like USB speakers to aid in listening to discussions, but obviously quality will be best-effort. This may work fine for small breakout sessions but will likely be inadequate for larger rooms.
Did I say Best Effort? That means there will not be full onsite technical support to troubleshoot audio or other issues related to remote connectivity. Please do not confuse your community architects with onsite IT. :)
As our event team works with the venue and A/V team, we will let you know if anything changes. Finally, one last bit of Unix philosophy: “Economy and elegance of design through resource constraints.” The pandemic lockdowns started suddenly, but we find that they’re not ending that way. Connecting in-person again turns out to be bumpy and sometimes painful. We’re all doing our best, as a set of communities under constraints. This can either be a source of conflict or a source of creativity. Our choice. None but ours. I appreciate everyone’s optimism, flexibility, and patience at this time as we all figure it out. Heather
-- Heather KirkseyVP, Ecosystem and Community LF Networking Mobile: +1.512.917.7938 IRC: HKirksey
|
|
|
Re: [release] Sulfur SR1 and Phosphorus SR3 announcement
|
|
|
Re: [release] Sulfur SR1 and Phosphorus SR3 announcement
|
|
|
Re: [release] Sulfur SR1 and Phosphorus SR3 announcement
Daniel de la Rosa
Hello Robert and all
On Mon, May 16, 2022 at 12:40 PM Robert Varga < nite@...> wrote: On 13/05/2022 07:38, Daniel de la Rosa wrote:
> Hello TSC and all
>
> We are going to code freeze Sulfur and Phosphorus for all Managed
> Projects ( cut and lock release branches ) on Monday May 16th at 10 am
> UTC. We are doing these two releases in parallel to catch up on the
> release schedule.
>
> Please remember that we only allow blocker bug fixes in release branch
> after code freezes
stable/sulfur has been updated with the MRI code drop.
we are still seeing these OFP issues ( and one BGPCEP) with sulfur for SR1.. Is there a jira ticket to fix these issues?
stable/magnesium has not been updated yet, but should get there tomorrow.
phosphorus looks ready for SR3. I'm going to pick AR #48 since it looks ready if everybody is ok with that
Regards,
Robert
|
|
|
Re: [release] Sulfur SR1 and Phosphorus SR3 announcement
On 13/05/2022 07:38, Daniel de la Rosa wrote: Hello TSC and all
We are going to code freeze Sulfur and Phosphorus for all Managed Projects ( cut and lock release branches ) on Monday May 16th at 10 am UTC. We are doing these two releases in parallel to catch up on the release schedule.
Please remember that we only allow blocker bug fixes in release branch after code freezes stable/sulfur has been updated with the MRI code drop. stable/magnesium has not been updated yet, but should get there tomorrow. Regards, Robert
|
|
|
Sulfur SR1 and Phosphorus SR3 announcement
Daniel de la Rosa
Hello TSC and all
We are going to code freeze Sulfur and Phosphorus for all Managed Projects ( cut and lock release branches ) on Monday May 16th at 10 am UTC. We are doing these two releases in parallel to catch up on the release schedule.
Please remember that we only allow blocker bug fixes in release branch after code freezes
Thanks -- Daniel de la Rosa ODL Release Manager
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status
Here it is :
Thanks to everyone that contributed to this release :)
Thanks Luis and Anil, So can we get a distribution now ? On Sun, May 8, 2022 at 5:40 PM Luis Gomez < ecelgp@...> wrote: Also, it looks like distribution jobs missed stable/sulfur update, I will need this merged in order to produce a release:
BR/Luis
Thanks for the update. If that's the case, @Luis Gomez please proceed to release Sulfur distribution at your earliest convenience
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 issues we are facing and that are still
under investigation. The bottom line is that a rather important number of our functional tests are still failing, and so it is not possible to release with so many functional regressions. On the other hand, if TransportPCE cannot integrate the GA, will it still be possible to integrate Sulfur SR1 or SR2 when problems have been resolved? If I try to summarize the situation and issues that are still open:
- Openroadm models compilation (assembling issue - see my email of 2022-04-27)
- Link augmentation writing in openroadm-topology (see my email of 2022-05-02; under investigation)
- Feature odl-transportpce-swagger no longer effective (would have an issue with our GNPy yang models?)
- Run time issue to run some Junit tests (see networkmodel/src/test/java/org/opendaylight/transportpce/networkmodel/service/FrequenciesServiceTest.java, pce/src/test/java/org/opendaylight/transportpce/pce/gnpy/GnpyUtilitiesImplTest.java
in change https://git.opendaylight.org/gerrit/c/transportpce/+/100646)
- Possible other failures on functional tests not investigated yet due to the blocking issue mentioned above…
Best regards, Gilles
Orange Restricted
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
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
On Tue, May 3, 2022 at 2:12 PM Anil Shashikumar Belur <abelur@...> wrote:
On Tue, May 3, 2022 at 1:45 PM Anil Shashikumar Belur <abelur@...> wrote:
Hello All,
OpenDaylight Sulfur version bump is complete and the staging repository has been promoted. The 'stable/sulfur' branch is unlocked and ready for development.
Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts for Sulfur.
2. Release Distribution once the 1. is complete.
3. Release notes - $project PTLs to submit release notes to Opendaylight docs.
4. Update ODL downloads page [1.].
Many thanks to everyone who contributed to the Sulfur release.
Regards,
Anil Belur
Orange Restricted
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status
Daniel de la Rosa
Thanks Luis and Anil, So can we get a distribution now ?
On Sun, May 8, 2022 at 5:40 PM Luis Gomez < ecelgp@...> wrote: Also, it looks like distribution jobs missed stable/sulfur update, I will need this merged in order to produce a release:
BR/Luis
Thanks for the update. If that's the case, @Luis Gomez please proceed to release Sulfur distribution at your earliest convenience
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 issues we are facing and that are still
under investigation. The bottom line is that a rather important number of our functional tests are still failing, and so it is not possible to release with so many functional regressions. On the other hand, if TransportPCE cannot integrate the GA, will it still be possible to integrate Sulfur SR1 or SR2 when problems have been resolved? If I try to summarize the situation and issues that are still open:
- Openroadm models compilation (assembling issue - see my email of 2022-04-27)
- Link augmentation writing in openroadm-topology (see my email of 2022-05-02; under investigation)
- Feature odl-transportpce-swagger no longer effective (would have an issue with our GNPy yang models?)
- Run time issue to run some Junit tests (see networkmodel/src/test/java/org/opendaylight/transportpce/networkmodel/service/FrequenciesServiceTest.java, pce/src/test/java/org/opendaylight/transportpce/pce/gnpy/GnpyUtilitiesImplTest.java
in change https://git.opendaylight.org/gerrit/c/transportpce/+/100646)
- Possible other failures on functional tests not investigated yet due to the blocking issue mentioned above…
Best regards, Gilles
Orange Restricted
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
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
On Tue, May 3, 2022 at 2:12 PM Anil Shashikumar Belur <abelur@...> wrote:
On Tue, May 3, 2022 at 1:45 PM Anil Shashikumar Belur <abelur@...> wrote:
Hello All,
OpenDaylight Sulfur version bump is complete and the staging repository has been promoted. The 'stable/sulfur' branch is unlocked and ready for development.
Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts for Sulfur.
2. Release Distribution once the 1. is complete.
3. Release notes - $project PTLs to submit release notes to Opendaylight docs.
4. Update ODL downloads page [1.].
Many thanks to everyone who contributed to the Sulfur release.
Regards,
Anil Belur
Orange Restricted
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
|
|
|
TSC Meeting for May 12, 2022 at 10 pm Pacific
Hello OpenDaylight Community,
The next TSC meeting is May 12, 2022 at 10 pm Pacific Time.
As usual, the agenda proposal and the connection details for this meeting are available in the wiki
at the following URL:
If you need to add anything, please let me know or add it there.
The meeting minutes will be at the same location after the meeting is over.
Best Regards
Guillaume
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
|
|
|
Re: [integration-dev] [opendaylight-dev][release] OpenDaylight - Sulfur release status
Please review the following CR that adds a new job for chlorine stream on JDK17/CentOS8.
IIRC openjdk17 is going to be supported for chlorine, while the release was approved with openjdk11. We only have a single AR job that is building with openjdk11 for Chlorine, we should probably change this to support JDK11 and/or JDK17. On Mon, May 9, 2022 at 6:17 PM Ivan Hrasko <ivan.hrasko@...> wrote:
The patch is using openjdk11 also for chlorine?
Is that correct?
I was expecting openjdk 17.
Best,
Ivan
Od: integration-dev@... <integration-dev@...> v mene používateľa Luis Gomez <ecelgp@...>
Odoslané: pondelok, 9. mája 2022 2:39:57
Komu: Daniel de la Rosa
Kópia: THOUENON Gilles TGI/OLN; LAMBERT Guillaume INNOV/NET; Anil Shashikumar Belur; integration-dev@...; Release; OpenDaylight Discuss; TSC; Casey Cain; Andrew Grimberg; Transportpce-dev@...
Predmet: Re: [integration-dev] [opendaylight-dev][release] OpenDaylight - Sulfur release status
Also, it looks like distribution jobs missed stable/sulfur update, I will need this merged in order to produce a release:
BR/Luis
Thanks for the update. If that's the case, @Luis Gomez please proceed to release Sulfur distribution at your earliest convenience
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 issues we are facing and that are
still under investigation.
The bottom line is that a rather important number of our functional tests are still failing, and so it is not possible to release with so many functional regressions.
On the other hand, if TransportPCE cannot integrate the GA, will it still be possible to integrate Sulfur SR1 or SR2 when problems have been resolved?
If I try to summarize the situation and issues that are still open:
- Openroadm models compilation (assembling issue - see my email of 2022-04-27)
- Link augmentation writing in openroadm-topology (see my email of 2022-05-02; under investigation)
- Feature odl-transportpce-swagger no longer effective (would have an issue with our GNPy yang models?)
- Run time issue to run some Junit tests (see networkmodel/src/test/java/org/opendaylight/transportpce/networkmodel/service/FrequenciesServiceTest.java, pce/src/test/java/org/opendaylight/transportpce/pce/gnpy/GnpyUtilitiesImplTest.java
in change https://git.opendaylight.org/gerrit/c/transportpce/+/100646)
- Possible other failures on functional tests not investigated yet due to the blocking issue mentioned above…
Best regards,
Gilles
Orange Restricted
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
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
On Tue, May 3, 2022 at 2:12 PM Anil Shashikumar Belur <abelur@...> wrote:
On Tue, May 3, 2022 at 1:45 PM Anil Shashikumar Belur <abelur@...> wrote:
Hello All,
OpenDaylight Sulfur version bump is complete and the staging repository has been promoted. The 'stable/sulfur' branch is unlocked and ready for development.
Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts for Sulfur.
2. Release Distribution once the 1. is complete.
3. Release notes - $project PTLs to submit release notes to Opendaylight docs.
4. Update ODL downloads page [1.].
Many thanks to everyone who contributed to the Sulfur release.
Regards,
Anil Belur
Orange Restricted
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
|
|
|
Re: [integration-dev] [opendaylight-dev][release] OpenDaylight - Sulfur release status
IIRC openjdk17 is going to be supported for chlorine, while the release was approved with openjdk11. We only have a single AR job that is building with openjdk11 for Chlorine, we should probably change this to support JDK11 and/or JDK17.
On Mon, May 9, 2022 at 6:17 PM Ivan Hrasko <ivan.hrasko@...> wrote:
The patch is using openjdk11 also for chlorine?
Is that correct?
I was expecting openjdk 17.
Best,
Ivan
Od: integration-dev@... <integration-dev@...> v mene používateľa Luis Gomez <ecelgp@...>
Odoslané: pondelok, 9. mája 2022 2:39:57
Komu: Daniel de la Rosa
Kópia: THOUENON Gilles TGI/OLN; LAMBERT Guillaume INNOV/NET; Anil Shashikumar Belur; integration-dev@...; Release; OpenDaylight Discuss; TSC; Casey Cain; Andrew Grimberg; Transportpce-dev@...
Predmet: Re: [integration-dev] [opendaylight-dev][release] OpenDaylight - Sulfur release status
Also, it looks like distribution jobs missed stable/sulfur update, I will need this merged in order to produce a release:
BR/Luis
Thanks for the update. If that's the case, @Luis Gomez please proceed to release Sulfur distribution at your earliest convenience
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 issues we are facing and that are
still under investigation.
The bottom line is that a rather important number of our functional tests are still failing, and so it is not possible to release with so many functional regressions.
On the other hand, if TransportPCE cannot integrate the GA, will it still be possible to integrate Sulfur SR1 or SR2 when problems have been resolved?
If I try to summarize the situation and issues that are still open:
- Openroadm models compilation (assembling issue - see my email of 2022-04-27)
- Link augmentation writing in openroadm-topology (see my email of 2022-05-02; under investigation)
- Feature odl-transportpce-swagger no longer effective (would have an issue with our GNPy yang models?)
- Run time issue to run some Junit tests (see networkmodel/src/test/java/org/opendaylight/transportpce/networkmodel/service/FrequenciesServiceTest.java, pce/src/test/java/org/opendaylight/transportpce/pce/gnpy/GnpyUtilitiesImplTest.java
in change https://git.opendaylight.org/gerrit/c/transportpce/+/100646)
- Possible other failures on functional tests not investigated yet due to the blocking issue mentioned above…
Best regards,
Gilles
Orange Restricted
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
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
On Tue, May 3, 2022 at 2:12 PM Anil Shashikumar Belur <abelur@...> wrote:
On Tue, May 3, 2022 at 1:45 PM Anil Shashikumar Belur <abelur@...> wrote:
Hello All,
OpenDaylight Sulfur version bump is complete and the staging repository has been promoted. The 'stable/sulfur' branch is unlocked and ready for development.
Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts for Sulfur.
2. Release Distribution once the 1. is complete.
3. Release notes - $project PTLs to submit release notes to Opendaylight docs.
4. Update ODL downloads page [1.].
Many thanks to everyone who contributed to the Sulfur release.
Regards,
Anil Belur
Orange Restricted
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
|
|
|
Re: [integration-dev] [opendaylight-dev][release] OpenDaylight - Sulfur release status
The patch is using openjdk11 also for chlorine?
Is that correct?
I was expecting openjdk 17.
Best,
Ivan
Od: integration-dev@... <integration-dev@...> v mene používateľa Luis Gomez <ecelgp@...>
Odoslané: pondelok, 9. mája 2022 2:39:57
Komu: Daniel de la Rosa
Kópia: THOUENON Gilles TGI/OLN; LAMBERT Guillaume INNOV/NET; Anil Shashikumar Belur; integration-dev@...; Release; OpenDaylight Discuss; TSC; Casey Cain; Andrew Grimberg; Transportpce-dev@...
Predmet: Re: [integration-dev] [opendaylight-dev][release] OpenDaylight - Sulfur release status
Also, it looks like distribution jobs missed stable/sulfur update, I will need this merged in order to produce a release:
toggle quoted messageShow quoted text
Thanks for the update. If that's the case, @Luis Gomez please proceed to release Sulfur distribution at your earliest convenience
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 issues we are facing and that are
still under investigation.
The bottom line is that a rather important number of our functional tests are still failing, and so it is not possible to release with so many functional regressions.
On the other hand, if TransportPCE cannot integrate the GA, will it still be possible to integrate Sulfur SR1 or SR2 when problems have been resolved?
If I try to summarize the situation and issues that are still open:
- Openroadm models compilation (assembling issue - see my email of 2022-04-27)
- Link augmentation writing in openroadm-topology (see my email of 2022-05-02; under investigation)
- Feature odl-transportpce-swagger no longer effective (would have an issue with our GNPy yang models?)
- Run time issue to run some Junit tests (see networkmodel/src/test/java/org/opendaylight/transportpce/networkmodel/service/FrequenciesServiceTest.java, pce/src/test/java/org/opendaylight/transportpce/pce/gnpy/GnpyUtilitiesImplTest.java
in change https://git.opendaylight.org/gerrit/c/transportpce/+/100646)
- Possible other failures on functional tests not investigated yet due to the blocking issue mentioned above…
Best regards,
Gilles
Orange Restricted
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
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
On Tue, May 3, 2022 at 2:12 PM Anil Shashikumar Belur <abelur@...> wrote:
On Tue, May 3, 2022 at 1:45 PM Anil Shashikumar Belur <abelur@...> wrote:
Hello All,
OpenDaylight Sulfur version bump is complete and the staging repository has been promoted. The 'stable/sulfur' branch is unlocked and ready for development.
Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts for Sulfur.
2. Release Distribution once the 1. is complete.
3. Release notes - $project PTLs to submit release notes to Opendaylight docs.
4. Update ODL downloads page [1.].
Many thanks to everyone who contributed to the Sulfur release.
Regards,
Anil Belur
Orange Restricted
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status
Also, it looks like distribution jobs missed stable/sulfur update, I will need this merged in order to produce a release:
Thanks for the update. If that's the case, @Luis Gomez please proceed to release Sulfur distribution at your earliest convenience
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 issues we are facing and that are still
under investigation. The bottom line is that a rather important number of our functional tests are still failing, and so it is not possible to release with so many functional regressions. On the other hand, if TransportPCE cannot integrate the GA, will it still be possible to integrate Sulfur SR1 or SR2 when problems have been resolved? If I try to summarize the situation and issues that are still open:
- Openroadm models compilation (assembling issue - see my email of 2022-04-27)
- Link augmentation writing in openroadm-topology (see my email of 2022-05-02; under investigation)
- Feature odl-transportpce-swagger no longer effective (would have an issue with our GNPy yang models?)
- Run time issue to run some Junit tests (see networkmodel/src/test/java/org/opendaylight/transportpce/networkmodel/service/FrequenciesServiceTest.java, pce/src/test/java/org/opendaylight/transportpce/pce/gnpy/GnpyUtilitiesImplTest.java
in change https://git.opendaylight.org/gerrit/c/transportpce/+/100646)
- Possible other failures on functional tests not investigated yet due to the blocking issue mentioned above…
Best regards, Gilles
Orange Restricted
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
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
On Tue, May 3, 2022 at 2:12 PM Anil Shashikumar Belur <abelur@...> wrote:
On Tue, May 3, 2022 at 1:45 PM Anil Shashikumar Belur <abelur@...> wrote:
Hello All,
OpenDaylight Sulfur version bump is complete and the staging repository has been promoted. The 'stable/sulfur' branch is unlocked and ready for development.
Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts for Sulfur.
2. Release Distribution once the 1. is complete.
3. Release notes - $project PTLs to submit release notes to Opendaylight docs.
4. Update ODL downloads page [1.].
Many thanks to everyone who contributed to the Sulfur release.
Regards,
Anil Belur
Orange Restricted
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status
TPCE can integrate in the ODL distribution any time they wish to do so.
I am curious: are all these issues due to changes in TPCE, changes in Kernel or both?
Thanks for the update. If that's the case, @Luis Gomez please proceed to release Sulfur distribution at your earliest convenience
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 issues we are facing and that are still
under investigation. The bottom line is that a rather important number of our functional tests are still failing, and so it is not possible to release with so many functional regressions. On the other hand, if TransportPCE cannot integrate the GA, will it still be possible to integrate Sulfur SR1 or SR2 when problems have been resolved? If I try to summarize the situation and issues that are still open:
- Openroadm models compilation (assembling issue - see my email of 2022-04-27)
- Link augmentation writing in openroadm-topology (see my email of 2022-05-02; under investigation)
- Feature odl-transportpce-swagger no longer effective (would have an issue with our GNPy yang models?)
- Run time issue to run some Junit tests (see networkmodel/src/test/java/org/opendaylight/transportpce/networkmodel/service/FrequenciesServiceTest.java, pce/src/test/java/org/opendaylight/transportpce/pce/gnpy/GnpyUtilitiesImplTest.java
in change https://git.opendaylight.org/gerrit/c/transportpce/+/100646)
- Possible other failures on functional tests not investigated yet due to the blocking issue mentioned above…
Best regards, Gilles
Orange Restricted
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
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
On Tue, May 3, 2022 at 2:12 PM Anil Shashikumar Belur <abelur@...> wrote:
On Tue, May 3, 2022 at 1:45 PM Anil Shashikumar Belur <abelur@...> wrote:
Hello All,
OpenDaylight Sulfur version bump is complete and the staging repository has been promoted. The 'stable/sulfur' branch is unlocked and ready for development.
Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts for Sulfur.
2. Release Distribution once the 1. is complete.
3. Release notes - $project PTLs to submit release notes to Opendaylight docs.
4. Update ODL downloads page [1.].
Many thanks to everyone who contributed to the Sulfur release.
Regards,
Anil Belur
Orange Restricted
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status
Daniel de la Rosa
Thanks for the update. If that's the case, @Luis Gomez please proceed to release Sulfur distribution at your earliest convenience
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 issues we are facing and that are still
under investigation.
The bottom line is that a rather important number of our functional tests are still failing, and so it is not possible to release with so many functional regressions.
On the other hand, if TransportPCE cannot integrate the GA, will it still be possible to integrate Sulfur SR1 or SR2 when problems have been resolved?
If I try to summarize the situation and issues that are still open:
- Openroadm models compilation (assembling issue - see my email of 2022-04-27)
- Link augmentation writing in openroadm-topology (see my email of 2022-05-02; under investigation)
- Feature odl-transportpce-swagger no longer effective (would have an issue with our GNPy yang models?)
- Run time issue to run some Junit tests (see networkmodel/src/test/java/org/opendaylight/transportpce/networkmodel/service/FrequenciesServiceTest.java, pce/src/test/java/org/opendaylight/transportpce/pce/gnpy/GnpyUtilitiesImplTest.java
in change https://git.opendaylight.org/gerrit/c/transportpce/+/100646)
- Possible other failures on functional tests not investigated yet due to the blocking issue mentioned above…
Best regards,
Gilles
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
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
On Tue, May 3, 2022 at 2:12 PM Anil Shashikumar Belur <abelur@...> wrote:
On Tue, May 3, 2022 at 1:45 PM Anil Shashikumar Belur <abelur@...> wrote:
Hello All,
OpenDaylight Sulfur version bump is complete and the staging repository has been promoted. The 'stable/sulfur' branch is unlocked and ready for development.
Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts for Sulfur.
2. Release Distribution once the 1. is complete.
3. Release notes - $project PTLs to submit release notes to Opendaylight docs.
4. Update ODL downloads page [1.].
Many thanks to everyone who contributed to the Sulfur release.
Regards,
Anil Belur
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
|
|
|
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 issues we are facing and that are still
under investigation.
The bottom line is that a rather important number of our functional tests are still failing, and so it is not possible to release with so many functional regressions.
On the other hand, if TransportPCE cannot integrate the GA, will it still be possible to integrate Sulfur SR1 or SR2 when problems have been resolved?
If I try to summarize the situation and issues that are still open:
- Openroadm models compilation (assembling issue - see my email of 2022-04-27)
- Link augmentation writing in openroadm-topology (see my email of 2022-05-02; under investigation)
- Feature odl-transportpce-swagger no longer effective (would have an issue with our GNPy yang models?)
- Run time issue to run some Junit tests (see networkmodel/src/test/java/org/opendaylight/transportpce/networkmodel/service/FrequenciesServiceTest.java, pce/src/test/java/org/opendaylight/transportpce/pce/gnpy/GnpyUtilitiesImplTest.java
in change https://git.opendaylight.org/gerrit/c/transportpce/+/100646)
- Possible other failures on functional tests not investigated yet due to the blocking issue mentioned above…
Best regards,
Gilles
De : release@... <release@...>
De la part de Guillaume Lambert via lists.opendaylight.org
Envoyé : mercredi 4 mai 2022 17:14
À : Daniel de la Rosa <ddelarosa0707@...>; Anil Shashikumar Belur <abelur@...>; THOUENON Gilles INNOV/NET <gilles.thouenon@...>
Cc : 'integration-dev@...' (integration-dev@...) (integration-dev@...) <integration-dev@...>; Release <release@...>; OpenDaylight Discuss <discuss@...>;
TSC <tsc@...>; Casey Cain <ccain@...>; Andrew Grimberg <agrimberg@...>; Luis Gomez <ecelgp@...>
Objet : 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
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
On Tue, May 3, 2022 at 2:12 PM Anil Shashikumar Belur <abelur@...> wrote:
On Tue, May 3, 2022 at 1:45 PM Anil Shashikumar Belur <abelur@...> wrote:
Hello All,
OpenDaylight Sulfur version bump is complete and the staging repository has been promoted. The 'stable/sulfur' branch is unlocked and ready for development.
Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts for Sulfur.
2. Release Distribution once the 1. is complete.
3. Release notes - $project PTLs to submit release notes to Opendaylight docs.
4. Update ODL downloads page [1.].
Many thanks to everyone who contributed to the Sulfur release.
Regards,
Anil Belur
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
|
|
|
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@...>
Envoyé : mercredi 4 mai 2022 16:41
À : Anil Shashikumar Belur <abelur@...>; LAMBERT Guillaume INNOV/NET <guillaume.lambert@...>
Cc : 'integration-dev@...' (integration-dev@...) (integration-dev@...) <integration-dev@...>; Release <release@...>; OpenDaylight Discuss <discuss@...>;
TSC <tsc@...>; Casey Cain <ccain@...>; Andrew Grimberg <agrimberg@...>; Luis Gomez <ecelgp@...>
Objet : 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
On Tue, May 3, 2022 at 2:12 PM Anil Shashikumar Belur <abelur@...> wrote:
On Tue, May 3, 2022 at 1:45 PM Anil Shashikumar Belur <abelur@...> wrote:
Hello All,
OpenDaylight Sulfur version bump is complete and the staging repository has been promoted. The 'stable/sulfur' branch is unlocked and ready for development.
Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts for Sulfur.
2. Release Distribution once the 1. is complete.
3. Release notes - $project PTLs to submit release notes to Opendaylight docs.
4. Update ODL downloads page [1.].
Many thanks to everyone who contributed to the Sulfur release.
Regards,
Anil Belur
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status
Daniel de la Rosa
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
On Tue, May 3, 2022 at 2:12 PM Anil Shashikumar Belur < abelur@...> wrote: +tsc
On Tue, May 3, 2022 at 1:45 PM Anil Shashikumar Belur < abelur@...> wrote: Hello All,
OpenDaylight Sulfur version bump is complete and the staging repository has been promoted. The 'stable/sulfur' branch is unlocked and ready for development.
Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts for Sulfur.
2. Release Distribution once the 1. is complete.
3. Release notes - $project PTLs to submit release notes to Opendaylight docs.
4. Update ODL downloads page [1.].
Many thanks to everyone who contributed to the Sulfur release.
Regards,
Anil Belur
|
|
|
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 following URL:
https://wiki.opendaylight.org/x/CnoEAQ
If you need to add anything, please let me know or add it there.
The meeting minutes will be at the same location after the meeting is over.
Best Regards
Guillaume
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
|
|
|
