Update the documentation link for doc migration
Change-Id: I82cdee6711fa98ef7632bea4763d5db21cb6dcc2
This commit is contained in:
parent
12144fbe78
commit
b840cd652c
|
@ -1,4 +1,4 @@
|
||||||
fuxi Style Commandments
|
fuxi Style Commandments
|
||||||
===============================================
|
===============================================
|
||||||
|
|
||||||
Read the OpenStack Style Commandments https://docs.openstack.org/developer/hacking/
|
Read the OpenStack Style Commandments https://docs.openstack.org/hacking/latest/
|
||||||
|
|
|
@ -20,7 +20,7 @@ the unified persistence storage provider for virtual machine, baremetal
|
||||||
and Docker container.
|
and Docker container.
|
||||||
|
|
||||||
* Free software: Apache license
|
* Free software: Apache license
|
||||||
* Documentation: https://docs.openstack.org/developer/fuxi
|
* Documentation: https://docs.openstack.org/fuxi/latest/
|
||||||
* Source: https://git.openstack.org/cgit/openstack/fuxi
|
* Source: https://git.openstack.org/cgit/openstack/fuxi
|
||||||
* Bugs: https://bugs.launchpad.net/fuxi
|
* Bugs: https://bugs.launchpad.net/fuxi
|
||||||
* Blueprints: https://blueprints.launchpad.net/fuxi
|
* Blueprints: https://blueprints.launchpad.net/fuxi
|
||||||
|
|
|
@ -98,4 +98,4 @@ References
|
||||||
|
|
||||||
* `Manila share features support mapping`_
|
* `Manila share features support mapping`_
|
||||||
|
|
||||||
.. _Manila share features support mapping: https://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html
|
.. _Manila share features support mapping: https://docs.openstack.org/manila/latest/devref/share_back_ends_feature_support_mapping.html
|
||||||
|
|
|
@ -4,7 +4,7 @@ Release Notes
|
||||||
What is reno ?
|
What is reno ?
|
||||||
--------------
|
--------------
|
||||||
|
|
||||||
Fuxi uses `reno <http://docs.openstack.org/developer/reno/usage.html>`_ for
|
Fuxi uses `reno <https://docs.openstack.org/reno/latest/user/usage.html>`_ for
|
||||||
providing release notes in-tree. That means that a patch can include a *reno
|
providing release notes in-tree. That means that a patch can include a *reno
|
||||||
file* or a series can have a follow-on change containing that file explaining
|
file* or a series can have a follow-on change containing that file explaining
|
||||||
what the impact is.
|
what the impact is.
|
||||||
|
@ -19,7 +19,7 @@ generated using the reno tool this way:
|
||||||
where usually ``<name-your-file>`` can be ``bp-<blueprint_name>`` for a
|
where usually ``<name-your-file>`` can be ``bp-<blueprint_name>`` for a
|
||||||
blueprint or ``bug-XXXXXX`` for a bugfix.
|
blueprint or ``bug-XXXXXX`` for a bugfix.
|
||||||
|
|
||||||
Refer to the `reno documentation <http://docs.openstack.org/developer/reno/usage.html#editing-a-release-note>`_
|
Refer to the `reno documentation <https://docs.openstack.org/reno/latest/user/usage.html#editing-a-release-note>`_
|
||||||
for the full list of sections.
|
for the full list of sections.
|
||||||
|
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue