openstack
/
shade
Code Issues Proposed changes

Update the url in doc 

Change-Id: Ifb2183870cff73c03c668926bad47bc131979918
This commit is contained in:
melissaml 2018-09-24 16:50:26 +08:00
parent b5084ad3a8
commit d0da0b0323
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
HACKING.rst
View File

@ -2,7 +2,7 @@ shade Style Commandments
======================== ========================
Read the OpenStack Style Commandments Read the OpenStack Style Commandments
http://docs.openstack.org/developer/hacking/ https://docs.openstack.org/hacking/latest/
Indentation Indentation
----------- -----------

2
doc/source/contributor/coding.rst
View File

@ -18,7 +18,7 @@ Below are the patterns that we expect Shade developers to follow.
Release Notes Release Notes
============= =============
Shade uses `reno <http://docs.openstack.org/developer/reno/>`_ for Shade uses `reno <https://docs.openstack.org/reno/latest/>`_ for
managing its release notes. A new release note should be added to managing its release notes. A new release note should be added to
your contribution anytime you add new API calls, fix significant bugs, your contribution anytime you add new API calls, fix significant bugs,
add new functionality or parameters to existing API calls, or make any add new functionality or parameters to existing API calls, or make any