On Apr 14, 2021, at 3:47 AM, guillaume.lambert@... wrote:

Hello

I've taken care of creating a self-assigned JIRA ticket to update the download pages.

They should now appear in the documentation web site.

I let you check if you see any problems.

By the way, I have also

• hidden in the documentation fly-out panel the "master" and  "magnesium" and "sodium" documentations 
  since they are doppelganger for "latest" or officially EOL now. (Thanks to Anil  who granted me the needed rights in RTD)
• updated the aluminium marketing announcement link from "https://www.opendaylight.org/current-release/aluminium" (unreachable and created with the old format up to Oxygen) 
  to the new format "https://www.opendaylight.org/current-release-aluminium"
  
• pre-provision "https://www.opendaylight.org/current-release-silicon" even if it is not ready yet
• cleaned-up  obsolete docs JIRA tickets and created missing branches aluminium and silicon in JIRA
• replaced Thanh by Luis as a project leader in JIRA. 
  I noticed that a few tickets were created recently and were automatically assigned to Thanh who is now holding back.
  Luis, I think you are more able than me to dispatch the docs tickets but feel free to send me back the ball.
  

Hope this helps

Best Regards

Guillaume

---

De : Anil Belur [abelur@...]
Envoyé : vendredi 9 avril 2021 02:15
À : Luis Gomez
Cc : Daniel de la Rosa; LAMBERT Guillaume TGI/OLN; ODL Docs; TSC
Objet : Re: [OpenDaylight TSC] Phosphorus release schedule update

Luis: I've created new stable/silicon branches on RTD and now ran a "recheck" the CR's. The branching issue is resolved now, while the verify job are still failing on linkcheck failures:

09:59:13 (line    7) broken    www.sphinx-doc.org', port=443): Max retries exceeded with url: /en/master/ (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f7387762978>: Failed to establish a new connection: [Errno -2] Name or service not known',))
09:59:13 (line  123) broken    www.sphinx-doc.org', port=443): Max retries exceeded with url: /en/master/usage/restructuredtext/basics.html (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f73879ada20>: Failed to establish a new connection: [Errno -2] Name or service not known',))
09:59:13 (line  355) broken    www.sphinx-doc.org', port=443): Max retries exceeded with url: /en/master/usage/restructuredtext/basics.html (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f73879ada20>: Failed to establish a new connection: [Errno -2] Name or service not known',))
09:59:13 (line    7) broken    www.sphinx-doc.org', port=443): Max retries exceeded with url: /en/master/usage/restructuredtext/basics.html (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f7387762128>: Failed to establish a new connection: [Errno -2] Name or service not known',))
09:59:13 (line  304) broken    www.sphinx-doc.org', port=443): Max retries exceeded with url: /en/master/usage/restructuredtext/roles.html (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f7387762780>: Failed to establish a new connection: [Errno -2] Name or service not known',))
09:59:13 (line  416) broken    www.sphinx-doc.org', port=443): Max retries exceeded with url: /en/master/usage/restructuredtext/basics.html (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f7387762128>: Failed to establish a new connection: [Errno -2] Name or service not known',))
09:59:13 (line  416) broken    www.sphinx-doc.org', port=443): Max retries exceeded with url: /en/master/ (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f7387762978>: Failed to establish a new connection: [Errno -2] Name or service not known',))

I'll continue to look into this an update here.

  

On Fri, Apr 9, 2021 at 5:23 AM Luis Gomez <ecelgp@...> wrote:

Anything we want to show for Silicon could be added to the docs stable/silicon branch, however nothing will show in the portal until Anil or LF IT adds the new branch in RTD.

BR/Luis 

On Apr 8, 2021, at 10:58 AM, Daniel de la Rosa <ddelarosa0707@...> wrote:

Thanks Guillaume, Could you or the documentation team also update the downloads page for Silicon?

https://docs.opendaylight.org/en/stable-aluminium/downloads.html

also update the documentation page to include stable/silicon on the side menu and here

https://docs.opendaylight.org/en/stable-silicon/release-process/release-schedule.html

Thanh used to do this so not sure who can take over that now

thanks

On Wed, Mar 31, 2021 at 2:52 AM <guillaume.lambert@...> wrote:

Hi Daniel

 

Sure, I will prepare a change for that.

Note that the docs master branch still points to Silicon for the moment.

We have to wait for the stable/silicon branch creation to make the master branch point to phosphorus and merge this change.

 

Best Regards

Guillaume

 

De : Daniel de la Rosa [mailto:ddelarosa0707@...] 
Envoyé : mercredi 31 mars 2021 06:44
À : ODL Docs
Cc : LAMBERT Guillaume TGI/OLN; TSC
Objet : Phosphorus release schedule update

 

Hello Documentation team

 

Could you please help me update ODL Phosphorus release schedule. Basically replace Aluminium with Phosphorus 

 

https://docs.opendaylight.org/en/latest/release-process/release-schedule.html

 

with these dates

 

 

 

 

Thanks 

_________________________________________________________________________________________________________________________

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.