openstack/neutron
Code Issues Proposed changes

Cleanup HACKING.rst

Browse Source 
* Point to new location for hacking doc
(http://docs.openstack.org/developer/hacking/)
* Remove openstack-common section because already in main hacking doc

Change-Id: I7fbcfe13469a75fed08700ccbe07fefbee33db22
This commit is contained in:
Joe Gordon 2013-11-11 10:32:34 -08:00
parent ad97c96e73
commit dad4a1d8f1
1 changed files with 1 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
HACKING.rst
View File

@ -2,7 +2,7 @@ Neutron Style Commandments
======================= =======================
- Step 1: Read the OpenStack Style Commandments - Step 1: Read the OpenStack Style Commandments
https://github.com/openstack-dev/hacking/blob/master/doc/source/index.rst http://docs.openstack.org/developer/hacking/
- Step 2: Read on - Step 2: Read on
Neutron Specific Commandments Neutron Specific Commandments
@ -26,18 +26,3 @@ All setUp and tearDown methods must upcall using the super() method.
tearDown methods should be avoided and addCleanup calls should be preferred. tearDown methods should be avoided and addCleanup calls should be preferred.
Never manually create tempfiles. Always use the tempfile fixtures from Never manually create tempfiles. Always use the tempfile fixtures from
the fixture library to ensure that they are cleaned up. the fixture library to ensure that they are cleaned up.
openstack-common
----------------
A number of modules from openstack-common are imported into the project.
These modules are "incubating" in openstack-common and are kept in sync
with the help of openstack-common's update.py script. See:
http://wiki.openstack.org/CommonLibrary#Incubation
The copy of the code should never be directly modified here. Please
always update openstack-common first and then run the script to copy
the changes across.