Date   

Re: [E] [OpenDaylight TSC] TSC Meeting for January 20, 2022 at 10 pm Pacific

Ghazisaidi, Navid
 

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 <guillaume.lambert=orange.com@...> wrote:

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 the following URL:

 

https://wiki.opendaylight.org/x/3DIEAQ


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: [E] Re: [OpenDaylight TSC] Log4Shell impacts on ODL releases

Chokka, Manoj
 

Hi Daniel,

Since the changes are already done, could you prioritize silicon-SR4 first and then others.

Thank you,

BR, Manoj

On Thu, Jan 20, 2022 at 4:01 PM Robert Varga <nite@...> wrote:
On 20/01/2022 08:26, Daniel de la Rosa wrote:
> Hello Robert

Hey Daniel,

> On Mon, Jan 10, 2022 at 5:42 AM Robert Varga <nite@...
> <mailto:nite@...>> wrote:
>
>     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 that:
>
>     - all release trains up to and including Aluminium are past their
>     End of
>     Life and will not be receiving a community-driven release
>
>     - Silicon is currently in its Security Support period past its last
>     scheduled Service Release, hence will receive an unscheduled
>     security-driven SR4 in near future
>
>
> We can review this in the TSC but I think we can release Silicon SR4
> after Phosphorus SR2 and before Sulfur. Thoughts?

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 okay to release.

Regards,
Robert






Re: Log4Shell impacts on ODL releases

Robert Varga
 

On 20/01/2022 08:26, Daniel de la Rosa wrote:
Hello Robert
Hey Daniel,

On Mon, Jan 10, 2022 at 5:42 AM Robert Varga <nite@... <mailto:nite@...>> wrote:
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 that:
- all release trains up to and including Aluminium are past their
End of
Life and will not be receiving a community-driven release
- Silicon is currently in its Security Support period past its last
scheduled Service Release, hence will receive an unscheduled
security-driven SR4 in near future
We can review this in the TSC but I think we can release Silicon SR4 after Phosphorus SR2 and before Sulfur. Thoughts?
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 okay to release.

Regards,
Robert


Re: Phosphorus SR2 code freeze

Robert Varga
 

On 20/01/2022 08:25, Daniel de la Rosa wrote:
Hello all
Hello Daniel,

@Robert Varga <mailto:nite@...> i think we can pick a Phosphorus SR2 RC this week but let me know your thoughts based on the current AR state
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

https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-phosphorus-mvn35-openjdk11/ <https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-phosphorus-mvn35-openjdk11/>
Thanks
On Mon, Jan 10, 2022 at 8:00 AM Daniel de la Rosa <ddelarosa0707@... <mailto:ddelarosa0707@...>> wrote:
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 fixes in release
branch after code freezes
Daniel de la Rosa
ODL Release Manager
Thanks
ps. Release schedule and checklist for your reference
https://wiki.opendaylight.org/display/ODL/Phosphorus+SR2+Release+Checklist
<https://wiki.opendaylight.org/display/ODL/Phosphorus+SR2+Release+Checklist>
https://docs.opendaylight.org/en/latest/release-process/release-schedule.html
<https://docs.opendaylight.org/en/latest/release-process/release-schedule.html>
--
Daniel de la Rosa
ODL Release Manager


Re: Log4Shell impacts on ODL releases

Daniel de la Rosa
 

Hello Robert 

On Mon, Jan 10, 2022 at 5:42 AM Robert Varga <nite@...> wrote:
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 that:

- all release trains up to and including Aluminium are past their End of
Life and will not be receiving a community-driven release

- Silicon is currently in its Security Support period past its last
scheduled Service Release, hence will receive an unscheduled
security-driven SR4 in near future

We can review this in the TSC but I think we can release Silicon SR4 after Phosphorus SR2 and before Sulfur. Thoughts? 
 

- Phosphorus is currently in its normal support period, hence will have
this (and other) issues resolved in the upcoming run-of-the-mill SR2

- Sulfur release train currently mirrors Phosphorus in the parts which
are affected, it will be updated at the same time and Sulfur GA will be
on par with Phosphorus SR2

Regards,
Robert






Re: Phosphorus SR2 code freeze

Daniel de la Rosa
 

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 state


Thanks

On Mon, Jan 10, 2022 at 8:00 AM Daniel de la Rosa <ddelarosa0707@...> wrote:
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 fixes in release branch after code freezes

Daniel de la Rosa
ODL Release Manager

Thanks

ps. Release schedule and checklist for your reference

https://wiki.opendaylight.org/display/ODL/Phosphorus+SR2+Release+Checklist

https://docs.opendaylight.org/en/latest/release-process/release-schedule.html

--
Daniel de la Rosa
ODL Release Manager


TSC Meeting for January 20, 2022 at 10 pm Pacific

Guillaume Lambert
 

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 the following URL:

 

https://wiki.opendaylight.org/x/3DIEAQ


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.


RTD Job - automation rule to activate branch/tag

Anil Belur
 

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 rules. 

For instance, I have created automation rules for Netconf project for activating
all tags/branch matching this regex: "^[vV]"

Custom match: ^[vV]
Version type: Tag
Action: Activate version

Custom match: ^[vV]
Version type: Branch
Action: Activate version


I've created the activation rules for Netconf branch hopefully, this should work.

Regards,
Anil Belur


Re: Unscheduled Silicon SR4 release

Daniel de la Rosa
 

Hello Robert and all. Sure but next tsc meeting is on January 20th. Hopefully this can wait until then 

Thanks 

On Mon, Jan 10, 2022 at 5:46 AM Robert Varga <nite@...> wrote:
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 to
integrate here: https://git.opendaylight.org/gerrit/q/topic:mri-silicon-sr4

I will raise the ticket to get the patches merged and we should be
releasing Silicon SR4 as soon as practical. Daniel, can you drive that
conversation at the next TSC meeting, please?

Thanks,
Robert





--
Daniel de la Rosa
ODL Release Manager


Phosphorus SR2 code freeze

Daniel de la Rosa
 

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 fixes in release branch after code freezes

Daniel de la Rosa
ODL Release Manager

Thanks

ps. Release schedule and checklist for your reference

https://wiki.opendaylight.org/display/ODL/Phosphorus+SR2+Release+Checklist

https://docs.opendaylight.org/en/latest/release-process/release-schedule.html
--
Daniel de la Rosa
ODL Release Manager


Unscheduled Silicon SR4 release

Robert Varga
 

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 to integrate here: https://git.opendaylight.org/gerrit/q/topic:mri-silicon-sr4

I will raise the ticket to get the patches merged and we should be releasing Silicon SR4 as soon as practical. Daniel, can you drive that conversation at the next TSC meeting, please?

Thanks,
Robert


Log4Shell impacts on ODL releases

Robert Varga
 

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 that:

- all release trains up to and including Aluminium are past their End of Life and will not be receiving a community-driven release

- Silicon is currently in its Security Support period past its last scheduled Service Release, hence will receive an unscheduled security-driven SR4 in near future

- Phosphorus is currently in its normal support period, hence will have this (and other) issues resolved in the upcoming run-of-the-mill SR2

- Sulfur release train currently mirrors Phosphorus in the parts which are affected, it will be updated at the same time and Sulfur GA will be on par with Phosphorus SR2

Regards,
Robert


Season's Greetings and TSC Meeting for January 6, 2022 at 10 pm Pacific

Guillaume Lambert
 

Hello OpenDaylight Community,

 

I would like to start this message by wishing you a happy new year.

May 2022 bring everyone more health and happiness and success.


The next TSC meeting is January 6 , 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:

 

https://wiki.opendaylight.org/x/5S4EAQ


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: [E] Re: Next TSC meeting

Guillaume Lambert
 

Hello


I join Luis to wish happy holidays to everyone in the OpenDaylight community !

Best Regards

Guillaume


De : TSC@... <TSC@...> de la part de Luis Gomez <ecelgp@...>
Envoyé : vendredi 17 décembre 2021 00:29:02
À : Ha, Sangwook
Cc : Casey Cain; Daniel de la Rosa; Ghazisaidi, Navid; TSC; LAMBERT Guillaume INNOV/NET
Objet : Re: [OpenDaylight TSC] [E] Re: Next TSC meeting
 
Happy holidays everyone 🍾🥂🥳


On Dec 16, 2021, at 9:42 AM, Sangwook Ha via lists.opendaylight.org <sangwook.ha=verizon.com@...> wrote:

Sorry, I missed the meeting - I didn't realize it's past 9am, and joined the meeting late but nobody was there.
Merry Christmas and Happy New Year! See you next year 🙂

Thanks,
Sangwook

On Thu, Dec 16, 2021 at 9:09 AM Casey Cain <ccain@...> wrote:
Sorry we couldn't get a chance to talk before the end of the year.  Sorry we couldn't get a chance to talk before the end of the year.  Merry Christmas and Happy New Year!  I hope everyone stays safe and we see you in early '22!

Best,
Casey Cain
Senior Technical Community Architect
Linux Foundation
_________________
WeChat: okaru6
WhatsApp: +1.503.779.4519


On Wed, Dec 15, 2021 at 1:11 PM Daniel de la Rosa <ddelarosa0707@...> wrote:
Luis and I won’t be able to make it either. 

Merry Christmas and Happy New Year to all of you

On Wed, Dec 15, 2021 at 8:40 AM Ghazisaidi, Navid <navid.ghazisaidi@...> wrote:
Hi All, 

I won't be able to attend tomorrow's meeting. Sangwook will proxy me.

Merry Christmas and Happy New Year everyone!

Regards,
Navid
-- 
Daniel de la Rosa
ODL Release Manager


_________________________________________________________________________________________________________________________

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: [E] Re: Next TSC meeting

Luis Gomez
 

Happy holidays everyone 🍾🥂🥳


On Dec 16, 2021, at 9:42 AM, Sangwook Ha via lists.opendaylight.org <sangwook.ha=verizon.com@...> wrote:

Sorry, I missed the meeting - I didn't realize it's past 9am, and joined the meeting late but nobody was there.
Merry Christmas and Happy New Year! See you next year 🙂

Thanks,
Sangwook

On Thu, Dec 16, 2021 at 9:09 AM Casey Cain <ccain@...> wrote:
Sorry we couldn't get a chance to talk before the end of the year.  Sorry we couldn't get a chance to talk before the end of the year.  Merry Christmas and Happy New Year!  I hope everyone stays safe and we see you in early '22!

Best,
Casey Cain
Senior Technical Community Architect
Linux Foundation
_________________
WeChat: okaru6
WhatsApp: +1.503.779.4519


On Wed, Dec 15, 2021 at 1:11 PM Daniel de la Rosa <ddelarosa0707@...> wrote:
Luis and I won’t be able to make it either. 

Merry Christmas and Happy New Year to all of you

On Wed, Dec 15, 2021 at 8:40 AM Ghazisaidi, Navid <navid.ghazisaidi@...> wrote:
Hi All, 

I won't be able to attend tomorrow's meeting. Sangwook will proxy me.

Merry Christmas and Happy New Year everyone!

Regards,
Navid
-- 
Daniel de la Rosa
ODL Release Manager



Re: [E] Re: Next TSC meeting

Sangwook Ha
 

Sorry, I missed the meeting - I didn't realize it's past 9am, and joined the meeting late but nobody was there.
Merry Christmas and Happy New Year! See you next year 🙂

Thanks,
Sangwook

On Thu, Dec 16, 2021 at 9:09 AM Casey Cain <ccain@...> wrote:
Sorry we couldn't get a chance to talk before the end of the year.  Sorry we couldn't get a chance to talk before the end of the year.  Merry Christmas and Happy New Year!  I hope everyone stays safe and we see you in early '22!

Best,
Casey Cain
Senior Technical Community Architect
Linux Foundation
_________________
WeChat: okaru6
WhatsApp: +1.503.779.4519


On Wed, Dec 15, 2021 at 1:11 PM Daniel de la Rosa <ddelarosa0707@...> wrote:
Luis and I won’t be able to make it either. 

Merry Christmas and Happy New Year to all of you

On Wed, Dec 15, 2021 at 8:40 AM Ghazisaidi, Navid <navid.ghazisaidi@...> wrote:
Hi All, 

I won't be able to attend tomorrow's meeting. Sangwook will proxy me.

Merry Christmas and Happy New Year everyone!

Regards,
Navid
--
Daniel de la Rosa
ODL Release Manager


Re: Next TSC meeting

Casey Cain
 

Sorry we couldn't get a chance to talk before the end of the year.  Sorry we couldn't get a chance to talk before the end of the year.  Merry Christmas and Happy New Year!  I hope everyone stays safe and we see you in early '22!

Best,
Casey Cain
Senior Technical Community Architect
Linux Foundation
_________________
WeChat: okaru6
WhatsApp: +1.503.779.4519


On Wed, Dec 15, 2021 at 1:11 PM Daniel de la Rosa <ddelarosa0707@...> wrote:
Luis and I won’t be able to make it either. 

Merry Christmas and Happy New Year to all of you

On Wed, Dec 15, 2021 at 8:40 AM Ghazisaidi, Navid <navid.ghazisaidi@...> wrote:
Hi All, 

I won't be able to attend tomorrow's meeting. Sangwook will proxy me.

Merry Christmas and Happy New Year everyone!

Regards,
Navid
--
Daniel de la Rosa
ODL Release Manager


TSC Meeting for December 16, 2021 at 9 am Pacific

Guillaume Lambert
 

Hello OpenDaylight Community,
Next TSC meeting is December 16, 2021 at 9 am Pacific Time.
The agenda proposal and the connection details for this meeting are available 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: Next TSC meeting

Daniel de la Rosa
 

Luis and I won’t be able to make it either. 

Merry Christmas and Happy New Year to all of you

On Wed, Dec 15, 2021 at 8:40 AM Ghazisaidi, Navid <navid.ghazisaidi@...> wrote:
Hi All, 

I won't be able to attend tomorrow's meeting. Sangwook will proxy me.

Merry Christmas and Happy New Year everyone!

Regards,
Navid
--
Daniel de la Rosa
ODL Release Manager


Next TSC meeting

Ghazisaidi, Navid
 

Hi All, 

I won't be able to attend tomorrow's meeting. Sangwook will proxy me.

Merry Christmas and Happy New Year everyone!

Regards,
Navid

321 - 340 of 14349