Re: [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status


Luis Gomez
 

Sodium SR4 common distribution is released here: https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/0.11.4/

Please proceed with post-release tasks.

BR/Luis


On Aug 28, 2020, at 9:42 AM, Daniel de la Rosa <ddelarosa0707@...> wrote:

Thank you very much Guillaume. 

Luis, we can now proceed with sodium sr4 distribution. 

Thank you all 

On Fri, Aug 28, 2020 at 6:01 AM <guillaume.lambert@...> wrote:
















Hi all



 



FYI, I successfully released old-transportpce 0.4.5 for Sodium SR4 this morning.



https://jenkins.opendaylight.org/releng/view/transportpce/job/transportpce-release-merge/lastBuild/



 



 



BR



Guillaume



 







De : LAMBERT Guillaume TGI/OLN




Envoyé : vendredi 28 août 2020 08:38


À : 'Luis Gomez'


Cc : Daniel de la Rosa; Anil Belur; TSC; Release; integration-dev@...; Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...


Objet : RE: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status







 



Hi Luis,



 



Thanks for the feedback. If so, I’ll take care of that today.



 



Guillaume



 







De : TSC@... [mailto:TSC@...]

De la part de Luis Gomez


Envoyé : jeudi 27 août 2020 17:44


À : LAMBERT Guillaume TGI/OLN


Cc : Daniel de la Rosa; Anil Belur; TSC; Release; integration-dev@...; Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...


Objet : Re: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status







 



Hi Guillaume,





 







Even if there is no changes in TPCE between Sodium SR3 and SR4, if you do not produce a release for Sodium SR4, any downstream picking ODL Sodium SR4 (e.g. ONAP) will not be able to run TPCE. TPCE 0.4.4 was compiled towards Sodium SR3 and

would only work in that version. 







 







BR/Luis 





 





On Aug 27, 2020, at 7:40 AM, Guillaume Lambert via

lists.opendaylight.org
<guillaume.lambert=orange.com@...> wrote:





 







Hi all







 







I raised the topic on our weekly meeting today and everybody agreed there is nothing more we can backport from our master and Magnesium branches

to Sodium SR4.







Though we can release new TPCE sodium SR4 artifacts with nothing more, I suspect there is no point to do it if our Sodium SR3 artifacts can also

be consumed in this new distribution.







If you don’t think so, let me know and I will take care of it.







 







Guillaume







 







De : TSC@... [mailto:TSC@...] De

la part de
 Daniel de la Rosa


Envoyé : mercredi 26 août 2020 17:52


À : Anil Belur


Cc : TSC; Release; 'integration-dev@...' (integration-dev@...)

(integration-dev@...); Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...


Objet : Re: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status







 









Hello All









 











SM projects, please let us know if you are done releasing on Sodium SR4, so we can move forward with the general distribution. and downloads page











 











 











Thanks











 











On Fri, Aug 21, 2020 at 3:18 AM Anil Belur <abelur@...> wrote:











Hello All,





OpenDaylight Sodium SR4 version bump is complete while the staging repository is still being promoted. Note: 'stable/sodium' branch is locked.







Pending activities for the release:


1. Release self-managed projects of Sodium SR4.


2. Release Distribution.


3. Merge release notes change [1.]. 


4. Update ODL downloads page.





[1.] https://git.opendaylight.org/gerrit/c/docs/+/92233














Thanks to everyone who contributed to the release.





Regards,


Anil Belur











 









_________________________________________________________________________________________________________________________


 


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.








Join integration-dev@lists.opendaylight.org to automatically receive all group messages.