https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/DOCS-42 docs <p>As we move versions of OpenDaylight to security-only patches and then unsupported, we should actively flag that fact in the docs for that version on all pages.</p> <p>For example Django docs look like this for insecure versions:<br/> <a href="https://docs.djangoproject.com/en/1.7/" class="external-link" target="_blank" rel="nofollow noopener">https://docs.djangoproject.com/en/1.7/</a></p> <p>And this for versions under development:<br/> <a href="https://docs.djangoproject.com/en/dev/" class="external-link" target="_blank" rel="nofollow noopener">https://docs.djangoproject.com/en/dev/</a></p> <p>Operating System: All<br/> Platform: All</p> DOCS-42

Allow for whole versions to be deprecated and end-of-lifed in read the docs

Bug Resolved Done Thanh Ha (zxiiro) Colin Dixon Tue, 27 Jun 2017 20:15:20 +0000 Mon, 4 Jun 2018 01:02:07 +0000 Mon, 4 Jun 2018 01:02:07 +0000 unspecified read the docs 0 2 0 minutes 30 minutes <p>Preliminary patch:<br/> <a href="https://git.opendaylight.org/gerrit/#/c/49856/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/49856/</a></p> <p>There has been a significant improvement in that patch <span class="error">&#91;0&#93;</span>. I have added it for stable/boron and stable/carbon branches as well. stable/beryllium is not allowing me to upload to Gerrit. </p> <p>Need help for stable/lithium and previous branches, they have a different workflow. Or for me, it makes sense that we ignore those.</p> <p>See the demo here <span class="error">&#91;1&#93;</span>. Try switching the versions.</p> <p><span class="error">&#91;0&#93;</span>: <a href="https://git.opendaylight.org/gerrit/#/c/49856/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/49856/</a><br/> <span class="error">&#91;1&#93;</span>: test-odl-docs.readthedocs.io</p> <p> <span class="image-wrap" style=""><a id="14366_thumb" href="https://jira.opendaylight.org/secure/attachment/14366/14366_Screenshot_20180119_162637.png" title="Screenshot_20180119_162637.png" file-preview-type="image" file-preview-id="14366" file-preview-title="Screenshot_20180119_162637.png"><img src="https://jira.opendaylight.org/secure/thumbnail/14366/_thumb_14366.png" style="border: 0px solid black" role="presentation"/></a></span> </p> <p>I tried setting unsupported in my local branch and I am left with a simple text message embedded into the page header. I think we need to make sure it generates something more noticeable by the end user before we can consume this patch.</p> <p>Fixed the issue with the patch. The class name for unsupported_warning did not match in the warning-header.css file causing the banner to not appear correctly.</p> Development External issue ID 8759 External issue URL Rank 0|i01p2v: