To be clear this has to be activated for every project, not just the top level OpenDaylight docs project. Every project that has "WARNING: unknown document:" in the verify job is due to them missing t

If the project has not triggered a RTD build in a while then RTD won't have an updated list. You'll need to login to RTD and trigger it to build any branch and that will force the list to get updated.

When branching a new release someone has to login to ReadTheDocs and activate the new version or branch of the docs for every single project in that list. ReadTheDocs does not automatically generate d

You can contribute the patch and a committer can merge it. Even better we can nominate and start a vote for you into committer status, we've had release managers as a committer on docs in the past and

Sphinx doesn't have native support for redirects, there's some plugins that attempt to add it but they seem clunky. In the past we maintained both the current stable/release and master branches by che

I can see there's some orphaned servers that don't appear to be getting deleted, from the Jenkins UI: Online since Nov 10th 2020 https://jenkins.opendaylight.org/releng/computer/prd-centos7-builder-8c

Hi TSC, Unfortunately the time has come for me to step down from my active roles in the ODL community. I plan to be available to help answer questions and help transition my roles to new maintainers b

We can turn it off completely but then we'll never know when a link is broken. Part of the reason this job occasionally breaks though is because it's checking so many links in the docs and the interne

Documentation bits have been updated and I've created the stable/aluminium branch. You should see the updates to the docs pages in about an hour or so once the CDN updates. One thing remains is I coul

I updated the downloads pages related to sodium. Regards, Thanh

On the ODL side of things, moving the regular build jobs will be the "easy" part as it's migrating some maven shell scripts to the new CI system. CSIT on the other hand would be the difficult part. I

See inline. (Include's Robert's fixes) Either way would require modifying JJB to support the new SCM system GitLab and the trigger mechanism would be quite a bit different than what we have with Gerri

The downloads page patch has been merged to update with the new links. https://git.opendaylight.org/gerrit/c/docs/+/92005 Regards, Thanh

I realized we always forget to also bump the documentation version in project's conf.yaml files. That ends today with this patch https://git.opendaylight.org/gerrit/c/releng/builder/+/92055 to include

Hi Everyone, The improved branch cutting job [0] is ready to be reviewed. I produced this test patch [3] which is the output of a mock branch cutting for the Phosphorus release, it's not intended to b

Hi Anil, Looks like patch [1] is not for the release notes but for the downloads page. This patch won't pass until the final distribution is released since we have a linkchecker in place now that conf

Hi Everyone, (Branching off this discussion from the "Aluminium code freeze" thread.) I had some time this weekend and I figured this is something that was worth spending time on considering it will s

Hi Everyone, Jenkins jobs have been updated with new silicon jobs that build master and Aluminium jobs are now building stable/aluminium. At this point patches have been proposed to the master branch

So a lot of this is actually automated and we have documentation on the branch cutting process here: https://docs.opendaylight.org/en/latest/release-process/branch-cutting.html#autorelease So there's

Hi Everyone, An update of what's happening now. All of the autorelease managed projects should now have their stable/aluminium branches cut. Jobs are not yet available though so "master" will still ru