|
Re: [release] Silicon: next steps for Genius
Daniel de la Rosa
Robert and team
I'm still seeing Genius in AR... this is from the logs
Is this expected?
On Mon, Feb 1, 2021 at 2:43 PM Robert Varga < nite@...> wrote: Hello,
the patches to take Genius to self-managed mode in Silicon live here:
https://git.opendaylight.org/gerrit/q/topic:genius-sm
There are three patches now, which need to go in order:
- int/dist
- releng/builder
- releng/autorelease
The last one will trigger Jenkins proposing a patch to releng/builder,
which will finalize the transaction.
Regards,
Robert
On 29/01/2021 23:38, Robert Varga wrote:
> Thanks, we will proceed then with this plan.
>
> Regards,
> Robert
>
>
> On 29/01/2021 07:56, Hema Gopalakrishnan via lists.opendaylight.org wrote:
>> Hi Robert,
>>
>> The steps that you have mentioned below is fine with us. Please go ahead.
>>
>> Thanks,
>> Hema
>>
>> -----Original Message-----
>> From: Robert Varga <nite@...>
>> Sent: Tuesday, January 26, 2021 2:01 PM
>> To: tsc@...; release@...
>> Cc: Hema Gopalkrishnan <hema.gopalkrishnan@...>; Faseela K <k.faseela@...>; Chetan Arakere Gowdru <chetan.arakere@...>
>> Subject: Silicon: next steps for Genius
>>
>> Hello everyone,
>>
>> as you may be aware, Genius has decided not to participate in Silicon release as a managed project.
>>
>> As it currently stands it would be subject to branching and version-bumping at the Silicon branch and release points.
>>
>> We do not want that to happen, as would result in genius.git/master to become eventually unbuildable -- raising a high barrier of entry if someone were to want give it a try. This has happened to each and every ex-MSI project. We need and can do better.
>>
>> What we want to achieve is that as soon as Silicon releases, genius.git/master will be bumped to Silicon GA artifacts of its upstreams. That way its build will not get broken once Silicon SNAPSHOT artifacts expire and will remain buildable for pretty much eternity.
>>
>> To get to that point, we need to remove Genius from autorelease and int/dist before the Silicon branch point.
>>
>> Any objections to doing that this or next week?
>>
>> Regards,
>> Robert
>>
>>
>>
>>
>>
>
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Aluminium SR3 release status
OK, Aluminium SR3 release is here:
We can proceed with regular post-release actions.
BR/Luis
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
Ok now that TransportPCE is done, @Luis Gomez will move forward with distribution once he fixes some issues with the snapshots artifacts.
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
Anil and all. It was decided today to move forward with AR #370 as Aluminium SR3
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.
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:
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:
_________________________________________________________________________________________________________________________
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 - Aluminium SR3 release status
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
Ok now that TransportPCE is done, @Luis Gomez will move forward with distribution once he fixes some issues with the snapshots artifacts.
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
Anil and all. It was decided today to move forward with AR #370 as Aluminium SR3
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.
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:
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:
_________________________________________________________________________________________________________________________
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 - Aluminium SR3 release status
Daniel de la Rosa
Ok now that TransportPCE is done, @Luis Gomez will move forward with distribution once he fixes some issues with the snapshots artifacts.
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
Anil and all. It was decided today to move forward with AR #370 as Aluminium SR3
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.
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:
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:
_________________________________________________________________________________________________________________________
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: [release] Silicon code freeze
Daniel de la Rosa
Thank you Robert and all
@Anil Belur Can you create a Silicon CSIT checklist so we can pick a RC?
I think that we can pick AR#228
On Mon, Mar 15, 2021 at 5:50 AM Robert Varga < nite@...> wrote: On 15/03/2021 09:35, Robert Varga wrote:
> On 15/03/2021 08:40, Anil Belur wrote:
>> Greetings Robert:
>
> Hello Anil,
>
>> The stable/silicon branch is locked. Please confirm if you are unable to
>> merge the changes.
>
> I did not realize I can, the patches are landing as I am writing this.
All the patches have landed, next AR should be good to go.
Thanks,
Robert
|
|
|
|
|
|
TSC Meeting for March 18, 2021 at 10 pm Pacific
Hello OpenDaylight Community,
Next TSC meeting is March 18, 2021 at 10 pm 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.
Also congratulations and welcome aboard to our new TSC members Navid Ghazisaidi and Oleksii Mozghovyi !
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.
|
|
|
Call for Mentors and Projects for 2021 LF Networking Mentorship Program
Today, we’re excited to open the call for mentors and project proposals for the 2021 LF Networking Mentorship Program. This is the first year we're bringing all community intern/mentor projects under the LF Networking umbrella to launch with an integrated program schedule and program operations/management. The Program is intended to provide a formal structure to connect mentors and student developers from around the globe to contribute their enthusiasm, time, and experience toward building sustainable LFN communities. Why should you consider mentoring for LF Networking Mentorship Program?- You believe in the value of mentorship in helping new developers to navigate open source development, the culture, the tooling and infrastructure to be a productive member of the community.
- You are passionate about teaching and guiding student developers, many of whom may be first time open-source contributors,
- You are eager to bring in new perspectives, new ideas, and new talent into your community and projects.
- You have a narrowly scoped mentorship project with clear learning objectives/outcomes and a mentee's work and potential contributions could add value to the project or community of which you're an active developer or maintainer.
I am interested in mentoring but how do I get started? What are the elements the LFN Mentorship Program will implement to maximize mentor/mentee collaboration success? - Mentor and mentee onboarding will be conducted at the start of the Program
- Mentor and mentee guide will be available as part of the Linux Foundation CommunityBridge Mentorship initiative
- Project planning that includes deliverables, milestones, and tasks will be completed collaboratively between the mentors and mentees during the first two weeks of the program and posted on the wiki to increase transparency and accountability.
- Mentee presentations will be required to sharpen both presentation skills and to cultivate the ability to provide constructive feedback and critique that’s the norm in the open source community for developing technologies collaboratively and openly.
- Mentee evaluation will be conducted on a regular cadence tied to milestone deliverable schedules to help mentors and LFN staff formalize and respond to progress.
While mentors will be on a voluntary basis, the hired mentees will be eligible to receive a stipend. As an added bonus, each mentee who successfully completes the Program will be invited and financially sponsored by LF Networking to attend an event/conference and present their work to the broader community (specific event TBD with exemptions allowing for health and safety concerns.).
We look forward to your submission of a mentorship project and thank you in advance for volunteering your time to contribute to the training of the new talent pool in the LF Networking communities.
Best, Casey Cain Technical Program Manager / Community Architect Linux Foundation _________________ IRC: CaseyLF WeChat: okaru6 Voice: +1.408.641.0193
|
|
|
Re: 2021 TSC Election Results
Congrats Navid and Oleksii.
On Sat, Mar 13, 2021 at 2:19 AM Casey Cain < ccain@...> wrote: Hello, everyone.
Please join me in congratulating our
new members of the OpenDaylight Technical Steering Committee. Navid Ghazisaidi (Verizon) Oleksii Mozghovyi (Pantheon.tech)
We look forward to both candidates' leadership in the OpenDaylight Community!
Best, Casey Cain Technical Program Manager / Community Architect Linux Foundation _________________ IRC: CaseyLF WeChat: okaru6 Voice: +1.408.641.0193
|
|
|
Re: [release] Silicon code freeze
On 15/03/2021 09:35, Robert Varga wrote: On 15/03/2021 08:40, Anil Belur wrote:
Greetings Robert: Hello Anil,
The stable/silicon branch is locked. Please confirm if you are unable to
merge the changes. I did not realize I can, the patches are landing as I am writing this. All the patches have landed, next AR should be good to go. Thanks, Robert
|
|
|
Re: [release] Silicon code freeze
On 15/03/2021 08:40, Anil Belur wrote: Greetings Robert: Hello Anil, The stable/silicon branch is locked. Please confirm if you are unable to
merge the changes. I did not realize I can, the patches are landing as I am writing this. Thanks, Robert
Cheers,
Anil
On Fri, Mar 12, 2021 at 6:11 PM Robert Varga <nite@...
<mailto:nite@...>> wrote:
On 12/03/2021 06:28, Robert Varga wrote:
> Hey Daniel,
>
> sorry for the delay, the NETCONF bits were more challenging than
> expected and there were also some delays releasing it.
>
> Nevertheless it is hitting Maven Central now so I expect to have
things
> integrated today (CET).
The patches are staged here:
https://git.opendaylight.org/gerrit/q/topic:mri-silicon-ga
<https://git.opendaylight.org/gerrit/q/topic:mri-silicon-ga>
Request for supercommitter rights is here:
https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-21703
<https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-21703>
As soon as the rights are granted I'll merge the patches.
Regards,
Robert
|
|
|
Re: [release] Silicon code freeze
Greetings Robert:
The stable/silicon branch is locked. Please confirm if you are unable to merge the changes.
Cheers, Anil
|
|
|
Re: 2021 TSC Election Results
Venkatrangan Govindarajan
Congratulations Navid and Oleksii.Welcome to TSC. Let us work together to dominate the SDN world with ODL
|
|
|
Re: 2021 TSC Election Results
Congratulations and welcome to the TSC!!!
On Mar 12, 2021, at 8:19 AM, Casey Cain < ccain@...> wrote:
Hello, everyone.
Please join me in congratulating our
new members of the OpenDaylight Technical Steering Committee. Navid Ghazisaidi (Verizon)
We look forward to both candidates' leadership in the OpenDaylight Community!
Best, Casey Cain Technical Program Manager / Community Architect Linux Foundation _________________ IRC: CaseyLF WeChat: okaru6 Voice: +1.408.641.0193
|
|
|
Re: 2021 TSC Election Results
Congratulations Navid and Oleksii !
On Fri, Mar 12, 2021 at 8:19 AM Casey Cain < ccain@...> wrote: Hello, everyone.
Please join me in congratulating our
new members of the OpenDaylight Technical Steering Committee. Navid Ghazisaidi (Verizon) Oleksii Mozghovyi (Pantheon.tech)
We look forward to both candidates' leadership in the OpenDaylight Community!
Best, Casey Cain Technical Program Manager / Community Architect Linux Foundation _________________ IRC: CaseyLF WeChat: okaru6 Voice: +1.408.641.0193
|
|
|
Re: [E] [OpenDaylight TSC] 2021 TSC Election Results
Hello, everyone,
Thank you, Casey, and the TSC team members! I’m looking forward to working with you together.
Thanks,
Oleksii
|
|
|
Re: [E] [OpenDaylight TSC] 2021 TSC Election Results
Thanks Casey and TSC!
Looking forward to continue working with you all.
From: <TSC@...> on behalf of Casey Cain <ccain@...>
Date: Friday, March 12, 2021 at 8:19 AM
To: TSC <TSC@...>
Subject: [E] [OpenDaylight TSC] 2021 TSC Election Results
Hello, everyone.
Please join me in congratulating our new members of the OpenDaylight Technical Steering Committee.
Navid Ghazisaidi (Verizon)
Oleksii Mozghovyi (Pantheon.tech)
We look forward to both candidates' leadership in the OpenDaylight Community!
Casey Cain
Technical Program Manager / Community Architect
|
|
|
2021 TSC Election Results
Hello, everyone.
Please join me in congratulating our
new members of the OpenDaylight Technical Steering Committee. Navid Ghazisaidi (Verizon) Oleksii Mozghovyi (Pantheon.tech)
We look forward to both candidates' leadership in the OpenDaylight Community!
Best, Casey Cain Technical Program Manager / Community Architect Linux Foundation _________________ IRC: CaseyLF WeChat: okaru6 Voice: +1.408.641.0193
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Aluminium SR3 release status
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
toggle quoted message
Show quoted text
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
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.
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:
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:
_________________________________________________________________________________________________________________________
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: [release] Silicon code freeze
|
|
|
