openstack/neutron
Code Issues Proposed changes

Avoid referencing code from master branch

Browse Source 
I clicked on this link while reading the plugin development section in
the effective neutron guide.  I wasn't sure it linked me to the right
thing because it currently links to a blank line.  I figured that it
was just a line off but I wasn't sure because the link is to the
master branch, which can change.

This patch changes master to the short commit id of the commit that
added this link in the first place.  This way, it'll always link to
what it originally linked to.  If contents move around on master by
adding code to the file or refactoring or whatever, it might still
cause some confusion but at least we'll know what it was originally
intended to point to without doubt.

Change-Id: I13a10e10a31b88cb6f030ca644ca20e0bf14012c
This commit is contained in:
Carl Baldwin 2016-04-14 09:39:11 -06:00
parent 81c61a9939
commit f9c2b56518
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/devref/effective_neutron.rst
View File

@ -75,7 +75,7 @@ Document common pitfalls as well as good practices done during plugin developmen
there is an agent on the other side of the message broker that interacts
with the server. Plugins may not rely on `agents <https://review.openstack.org/#/c/174020/>`_ at all.
* Be mindful of required capabilities when you develop plugin extensions. The
`Extension description <https://github.com/openstack/neutron/blob/master/neutron/api/extensions.py#L122>`_ provides the ability to specify the list of required capabilities
`Extension description <https://github.com/openstack/neutron/blob/b14c06b5/neutron/api/extensions.py#L122>`_ provides the ability to specify the list of required capabilities
for the extension you are developing. By declaring this list, the server will
not start up if the requirements are not met, thus avoiding leading the system
to experience undetermined behavior at runtime.