cleanup HACKING.rst
A previous commit [1] removed two custom rules that were no longer necessary, but did not remove their notation in HACKING.rst. This cleans that up. It also removes wording that is duplicating nova's HACKING.rst, since we already explicitly state "Follow the nova HACKING.rst". [1] 9b3abb325b3b8a7a67981af9046f3b78e61bd2db Change-Id: I83bd9b8dcb39dd23e41288df11f46b381a49a2c7
This commit is contained in:
parent
bb7162b26d
commit
6b45aebe62
21
HACKING.rst
21
HACKING.rst
@ -1,25 +1,4 @@
|
||||
Nova-PowerVM Style Commandments
|
||||
===============================
|
||||
|
||||
- Step 1: Read the OpenStack Style Commandments
|
||||
https://docs.openstack.org/hacking/latest/
|
||||
- Step 2: Read on
|
||||
|
||||
Nova-PowerVM Specific Commandments
|
||||
----------------------------------
|
||||
- Follow the Nova HACKING.rst
|
||||
|
||||
- [P301] LOG.warn() is not allowed. Use LOG.warning()
|
||||
- [P302] Deprecated library function os.popen()
|
||||
|
||||
|
||||
Creating Unit Tests
|
||||
-------------------
|
||||
For every new feature, unit tests should be created that both test and
|
||||
(implicitly) document the usage of said feature. If submitting a patch for a
|
||||
bug that had no unit test, a new passing unit test should be added. If a
|
||||
submitted bug fix does have a unit test, be sure to add a new one that fails
|
||||
without the patch and passes with the patch.
|
||||
|
||||
For more information on creating unit tests and utilizing the testing
|
||||
infrastructure in OpenStack Nova, please read ``nova/tests/README.rst``.
|
||||
|
Loading…
x
Reference in New Issue
Block a user