On 10/11/2021 04:12, Luis Gomez wrote:

The release actually happened before the other projects because TPCE does not depend anymore on MSI projects. For future, I would still recommend TPCE to wait for the TSC release approval, otherwise there is risk of having to repeat the release if for a example a bug in the kernel is found.

Well, that's true, but then spinning a new release of a single project is quite straightforward, so TPCE can run as fast as kernel projects are integrated into int/dist -- it even could become an MRI project, if they so choose.

Regards,
Robert

BR/Luis

On Nov 9, 2021, at 5:47 PM, Daniel de la Rosa <ddelarosa0707@... <mailto:ddelarosa0707@...>> wrote:

HI Gilles,

This is from the other email thread.... The logs you show below are for a normal merge job that does not publish release artifacts but SNAPSHOT. So in short, you have bumped TPCE to use Silicon SR3 but the actual TPCE Silicon SR3 release does not happen until 1) Silicon SR3 release artifacts for all managed projects are published in nexus and 2) you execute this release merge job: https://jenkins.opendaylight.org/releng/view/transportpce/job/transportpce-release-merge <https://jenkins.opendaylight.org/releng/view/transportpce/job/transportpce-release-merge>

thanks

On Tue, Nov 9, 2021 at 7:09 AM <gilles.thouenon@... <mailto:gilles.thouenon@...>> wrote:

Hi Daniel,____

__ __

Shweta released TransportPCE SR3 last week. ____

Please see the following log :
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/transportpce-release-merge/23/
<https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/transportpce-release-merge/23/>____

At first sight it seems OK.____

Please tell us if there is any other action required from our side
(still the release note to update)____

__ __

Gilles____

__ __

__ __

*De :*integration-dev@...
<mailto:integration-dev@...>
[mailto:integration-dev@...
<mailto:integration-dev@...>] *De la part de*
Daniel de la Rosa
*Envoyé :* mardi 9 novembre 2021 15:53
*À :* Anil Belur <abelur@...
<mailto:abelur@...>>; LAMBERT Guillaume INNOV/NET
<guillaume.lambert@...
<mailto:guillaume.lambert@...>>; VACHHANI, SHWETA
(sv111y@... <mailto:sv111y@...>) <sv111y@...
<mailto:sv111y@...>>
*Cc :* 'integration-dev@...
<mailto:integration-dev@...>'
(integration-dev@...
<mailto:integration-dev@...>)
(integration-dev@...
<mailto:integration-dev@...>)
<integration-dev@...
<mailto:integration-dev@...>>; Andrew Grimberg
<agrimberg@...
<mailto:agrimberg@...>>; Casey Cain
<ccain@... <mailto:ccain@...>>;
OpenDaylight Discuss <discuss@...
<mailto:discuss@...>>; Release
<release@...
<mailto:release@...>>;
navid.ghazisaidi@... <mailto:navid.ghazisaidi@...>
*Objet :* Re: [integration-dev] [opendaylight-dev][release]
OpenDaylight - Silicon SR3 release status____

__ __

Thank you for the update. Guillaume and/or Shweta, please proceed
at your earliest convenience____

__ __

On Sun, Nov 7, 2021 at 4:09 PM Anil Belur
<abelur@... <mailto:abelur@...>>
wrote:____

Hello All,

OpenDaylight Silicon SR3 version bump is complete and the
staging repository is being promoted. The 'stable/silicon'
branch is unlocked.

Pending activities required to be complete for the release:
1. Self-managed projects to release artifacts for Silicon SR3.
2. Release Distribution once step 1. is complete.
3. Release notes merge CR.
https://git.opendaylight.org/gerrit/c/docs/+/98347
<https://git.opendaylight.org/gerrit/c/docs/+/98347>
4. Update ODL downloads page [1.].

Thanks to everyone who contributed to the Silicon SR3 release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html
<https://docs.opendaylight.org/en/latest/downloads.html>
[1.]
https://wiki.opendaylight.org/display/ODL/Silicon+SR3+Release+Approval
<https://wiki.opendaylight.org/display/ODL/Silicon+SR3+Release+Approval>____

-- ____

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.