Hello Robert and all. Sure but next tsc meeting is on January 20th. Hopefully this can wait until then 

Thanks 

On Mon, Jan 10, 2022 at 5:46 AM Robert Varga <nite@...> wrote:

Hello everyone,

as per my previous email, we need to spin an unscheduled security-driven
Service Release on the Silicon release train.

The MRI part of this is already done and the projects are ready to
integrate here: https://git.opendaylight.org/gerrit/q/topic:mri-silicon-sr4

I will raise the ticket to get the patches merged and we should be
releasing Silicon SR4 as soon as practical. Daniel, can you drive that
conversation at the next TSC meeting, please?

Thanks,
Robert

--

Daniel de la Rosa

ODL Release Manager

On Jan 24, 2022, at 3:43 PM, Anil Shashikumar Belur <abelur@...> wrote:

Greetings Luis:

I've run the script to activate all the projects. Please check and let me know if all the versions are active. 

Regards,

Anil

On Sun, Jan 23, 2022 at 4:39 AM Luis Gomez <ecelgp@...> wrote:

Hi Anil,

Is there anyone in ODL with admin permissions on all the RTD projects? If so, can this person generate a token and run this script to activate the stable-phosphorus branch on all the projects:

https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=activate-projects-rtd-branch.sh

I only have admin rights on distribution and I do not think at this moment we can afford to wait for all the project maintainers to do this individually.

Additionally, this admin person can add the rule you suggest to all the projects so that we do not need to run the script in future.

Once this is done, we can unblock this gerrit:

https://git.opendaylight.org/gerrit/c/docs/+/99193

BR/Luis

On Jan 12, 2022, at 3:53 PM, Anil Belur <abelur@...> wrote:

Hi all,

As discussed on the LFN Dev and testing forums, some of the RTD branches were not activated by default therefore the docs were not getting created. This can be solved by using Automation rules. 

For instance, I have created automation rules for Netconf project for activating

all tags/branch matching this regex: "^[vV]"

Custom match: ^[vV]
Version type: Tag
Action: Activate version

Custom match: ^[vV]
Version type: Branch
Action: Activate version

https://docs.readthedocs.io/en/stable/automation-rules.html

I've created the activation rules for Netconf branch hopefully, this should work.

Regards,

Anil Belur

On Jan 12, 2022, at 3:53 PM, Anil Belur <abelur@...> wrote:

Hi all,

As discussed on the LFN Dev and testing forums, some of the RTD branches were not activated by default therefore the docs were not getting created. This can be solved by using Automation rules. 

For instance, I have created automation rules for Netconf project for activating

all tags/branch matching this regex: "^[vV]"

Custom match: ^[vV]
Version type: Tag
Action: Activate version

Custom match: ^[vV]
Version type: Branch
Action: Activate version

https://docs.readthedocs.io/en/stable/automation-rules.html

I've created the activation rules for Netconf branch hopefully, this should work.

Regards,

Anil Belur

On Jan 12, 2022, at 3:53 PM, Anil Belur <abelur@...> wrote:

Hi all,

As discussed on the LFN Dev and testing forums, some of the RTD branches were not activated by default therefore the docs were not getting created. This can be solved by using Automation rules. 

For instance, I have created automation rules for Netconf project for activating

all tags/branch matching this regex: "^[vV]"

Custom match: ^[vV]
Version type: Tag
Action: Activate version

Custom match: ^[vV]
Version type: Branch
Action: Activate version

https://docs.readthedocs.io/en/stable/automation-rules.html

I've created the activation rules for Netconf branch hopefully, this should work.

Regards,

Anil Belur

Hello OpenDaylight Community,

The next TSC meeting is January 20 , 2022 at 10 pm Pacific Time.
As usual, the agenda proposal and the connection details for this meeting are available in the wiki
at the following URL:

 

https://wiki.opendaylight.org/x/3DIEAQ

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.

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.