On 20/01/2022 11:30, Robert Varga wrote:

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

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

Regards,
Robert

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

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

_________________________________________________________________________________________________________________________

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.

--

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

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

_________________________________________________________________________________________________________________________

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.

Happy holidays everyone 🍾🥂🥳

_________________________________________________________________________________________________________________________

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.