On Mar 23, 2021, at 12:03 AM, Robert Varga <nite@...> wrote:

On 19/03/2021 06:44, Daniel de la Rosa wrote:

Hello TSC

We have picked a Silicon AR #228 as release candidate. 

https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-silicon-mvn35-openjdk11/228/
<https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-silicon-mvn35-openjdk11/228/>

Here is the CSIT checklist so please review it ASAP

https://docs.google.com/spreadsheets/d/1zvD4xgiMlWCgg5ZBvxSRONY_LtLtzzNUeuA06-i7ukc/edit?usp=sharing
<https://docs.google.com/spreadsheets/d/1zvD4xgiMlWCgg5ZBvxSRONY_LtLtzzNUeuA06-i7ukc/edit?usp=sharing>

It looks like the netconf test suite is busted:

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netconf-csit-1node-scale-only-silicon/250/robot-plugin/log.html.gz

Suite setup failed:
Artifact "netconf-testtool" in component "netconf" could not be downloaded from https://nexus.opendaylight.org/content/repositories//autorelease-4768/org/opendaylight/netconf/netconf-testtool/1.13.1/netconf-testtool-1.13.1-rest-perf-client.jar

Also suite teardown failed:
Variable '${testtool}' not found.

Since NETCONF is an MRI project in Silicon, the testtool should not be
downloaded from autorelease staging repo but rather from normal release
repo.

I do not know how to achieve, can someone from int/test take a look?

Regards,
Robert

On Mar 18, 2021, at 6:02 PM, Luis Gomez via lists.opendaylight.org <ecelgp=gmail.com@...> wrote:

Yep, SNAPSHOT artifacts used in the common distribution have expired and got deleted because we let long time between Managed distribution release and Common distribution release.

This is the first time that this happens and has exposed some issues in the distribution repo. I will have to craft something in Jenkins to make this work, more info in tonight's meeting.

BR/Luis

On Mar 18, 2021, at 5:48 PM, Daniel de la Rosa <ddelarosa0707@...> wrote:

Ok now that TransportPCE is done, @Luis Gomez  will move forward with distribution once he fixes some issues with the snapshots artifacts. 

Thanks

On Fri, Mar 12, 2021 at 6:33 AM <guillaume.lambert@...> wrote:

Hello

 

Thanks Anil.  I just released TransportPCE v 2.3.0 for Al SR3.

Let me know if there is any issue with it.

 

Though I didn’t need to merge anything for Al SR3, it seems that tpce stable/aluminium branch still appears locked.

 

Best Regards

Guillaume

 

 

De : Anil Belur [mailto:abelur@...]
Envoyé : vendredi 12 mars 2021 03:49
À : Daniel de la Rosa
Cc : Casey Cain; LAMBERT Guillaume TGI/OLN; Luis Gomez; Release; Robert Varga; TSC
Objet : Re: [opendaylight-dev][release] OpenDaylight - Aluminium SR3 release status

 

Hello All,

OpenDaylight Aluminium SR3 version bump is complete and the staging repository has been promoted. The 'stable/aluminum' branch is unlocked and ready for development.

Pending activities that need to be completed for the release:
1. Self-managed projects release of Aluminum SR3.
2. Release Distribution once the 1. is complete.
3. Release notes - to be merged CR [1.]
4. Update ODL downloads page [0.].

Thanks to everyone who contributed to the release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html
[1.] https://git.opendaylight.org/gerrit/c/docs/+/95492

 

On Fri, Mar 12, 2021 at 10:07 AM Daniel de la Rosa <ddelarosa0707@...> wrote:

Anil and all. It was decided today to move forward with AR #370 as Aluminium SR3

 

Thanks 

 

On Wed, Mar 10, 2021 at 6:38 PM Anil Belur <abelur@...> wrote:

Hi Guillaume, 

 

+1, we can proceed with AR #370. Waiting on the other TSC members to weigh in.

 

Regards,

Anil

 

On Wed, Mar 10, 2021 at 8:49 PM <guillaume.lambert@...> wrote:

Hi Anil

 

Both options are fine in my opinion. What’s yours ?

With Silicon deadline coming soon, maybe AR #370 will be more straightforward.

 

Best regards

Guillaume

 

De : release@... [mailto:release@...] De la part de Anil Belur
Envoyé : mercredi 10 mars 2021 01:34
À : Daniel de la Rosa; TSC; Release
Cc : Luis Gomez; Robert Varga; Casey Cain
Objet : Re: [opendaylight-dev][release] OpenDaylight - Aluminium SR3 release status

 

 

 

On Mon, Mar 8, 2021 at 1:28 PM Anil Belur <abelur@...> wrote:

Greetings Team:

The version bump job for the Aluminimum SR3 release is failing, therefore we are blocked on the release till the outstanding issue with AR builds is resolved.

https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-version-bump-aluminium-mvn35-openjdk11/11/consoleFull

After digging around I have noticed that we have gone ahead with voting on the release without putting the code freeze in place beforehand. To proceed with the SR3 release, firstly we have to code freeze the Aluminium branch (which has been done now), resolve the outstanding issues with the AR builds #394 is failing.

[1.] https://jira.linuxfoundation.org/browse/IT-21671

Thanks,
Anil 

 

Hello TSC members:

 

The version bump issue has been resolved now with the below CR's. the version bump job is going through now in #12:

 

https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-version-bump-aluminium-mvn35-openjdk11/12/

https://git.opendaylight.org/gerrit/c/releng/builder/+/95455        
https://git.opendaylight.org/gerrit/c/releng/builder/+/95456

 

The question is if we can we proceed with releasing the existing AR #370 (as per vote: https://wiki.opendaylight.org/display/ODL/Aluminum+SR3+Release+Approval), since the staging repo has been promoted or do we need to go with a new AR, then we need to take the new AR build #395 and proceed with the CSIT checklist for #374.

 

AR #395: https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-aluminium-mvn35-openjdk11/395/

Integration test: https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-aluminium/374/

 

Regards,

Anil 

_________________________________________________________________________________________________________________________

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.

On Mar 18, 2021, at 5:48 PM, Daniel de la Rosa <ddelarosa0707@...> wrote:

Ok now that TransportPCE is done, @Luis Gomez  will move forward with distribution once he fixes some issues with the snapshots artifacts. 

Thanks

On Fri, Mar 12, 2021 at 6:33 AM <guillaume.lambert@...> wrote:

Hello

 

Thanks Anil.  I just released TransportPCE v 2.3.0 for Al SR3.

Let me know if there is any issue with it.

 

Though I didn’t need to merge anything for Al SR3, it seems that tpce stable/aluminium branch still appears locked.

 

Best Regards

Guillaume

 

 

De : Anil Belur [mailto:abelur@...]
Envoyé : vendredi 12 mars 2021 03:49
À : Daniel de la Rosa
Cc : Casey Cain; LAMBERT Guillaume TGI/OLN; Luis Gomez; Release; Robert Varga; TSC
Objet : Re: [opendaylight-dev][release] OpenDaylight - Aluminium SR3 release status

 

Hello All,

OpenDaylight Aluminium SR3 version bump is complete and the staging repository has been promoted. The 'stable/aluminum' branch is unlocked and ready for development.

Pending activities that need to be completed for the release:
1. Self-managed projects release of Aluminum SR3.
2. Release Distribution once the 1. is complete.
3. Release notes - to be merged CR [1.]
4. Update ODL downloads page [0.].

Thanks to everyone who contributed to the release.

Regards,
Anil Belur

[0.] https://docs.opendaylight.org/en/latest/downloads.html
[1.] https://git.opendaylight.org/gerrit/c/docs/+/95492

 

On Fri, Mar 12, 2021 at 10:07 AM Daniel de la Rosa <ddelarosa0707@...> wrote:

Anil and all. It was decided today to move forward with AR #370 as Aluminium SR3

 

Thanks 

 

On Wed, Mar 10, 2021 at 6:38 PM Anil Belur <abelur@...> wrote:

Hi Guillaume, 

 

+1, we can proceed with AR #370. Waiting on the other TSC members to weigh in.

 

Regards,

Anil

 

On Wed, Mar 10, 2021 at 8:49 PM <guillaume.lambert@...> wrote:

Hi Anil

 

Both options are fine in my opinion. What’s yours ?

With Silicon deadline coming soon, maybe AR #370 will be more straightforward.

 

Best regards

Guillaume

 

De : release@... [mailto:release@...] De la part de Anil Belur
Envoyé : mercredi 10 mars 2021 01:34
À : Daniel de la Rosa; TSC; Release
Cc : Luis Gomez; Robert Varga; Casey Cain
Objet : Re: [opendaylight-dev][release] OpenDaylight - Aluminium SR3 release status

 

 

 

On Mon, Mar 8, 2021 at 1:28 PM Anil Belur <abelur@...> wrote:

Greetings Team:

The version bump job for the Aluminimum SR3 release is failing, therefore we are blocked on the release till the outstanding issue with AR builds is resolved.

https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-version-bump-aluminium-mvn35-openjdk11/11/consoleFull

After digging around I have noticed that we have gone ahead with voting on the release without putting the code freeze in place beforehand. To proceed with the SR3 release, firstly we have to code freeze the Aluminium branch (which has been done now), resolve the outstanding issues with the AR builds #394 is failing.

[1.] https://jira.linuxfoundation.org/browse/IT-21671

Thanks,
Anil 

 

Hello TSC members:

 

The version bump issue has been resolved now with the below CR's. the version bump job is going through now in #12:

 

https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-version-bump-aluminium-mvn35-openjdk11/12/

https://git.opendaylight.org/gerrit/c/releng/builder/+/95455        
https://git.opendaylight.org/gerrit/c/releng/builder/+/95456

 

The question is if we can we proceed with releasing the existing AR #370 (as per vote: https://wiki.opendaylight.org/display/ODL/Aluminum+SR3+Release+Approval), since the staging repo has been promoted or do we need to go with a new AR, then we need to take the new AR build #395 and proceed with the CSIT checklist for #374.

 

AR #395: https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-aluminium-mvn35-openjdk11/395/

Integration test: https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-aluminium/374/

 

Regards,

Anil 

_________________________________________________________________________________________________________________________

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.