@@ -10,7 +10,8 @@ Cinder Client Specific Commandments
1010
1111General
1212-------
13- - Use 'raise' instead of 'raise e' to preserve original traceback or exception being reraised::
13+ - Use 'raise' instead of 'raise e' to preserve original traceback or exception
14+ being reraised::
1415
1516 except Exception as e:
1617 ...
@@ -22,26 +23,28 @@ General
2223
2324Release Notes
2425-------------
25- - Any patch that makes a change significant to the end consumer or deployer of an
26- OpenStack environment should include a release note (new features, upgrade impacts,
27- deprecated functionality, significant bug fixes, etc.)
26+ - Any patch that makes a change significant to the end consumer or deployer of
27+ an OpenStack environment should include a release note (new features, upgrade
28+ impacts, deprecated functionality, significant bug fixes, etc.)
2829
29- - Cinder Client uses Reno for release notes management. See the `Reno Documentation `_
30- for more details on its usage.
30+ - Cinder Client uses Reno for release notes management. See the `Reno
31+ Documentation `_ for more details on its usage.
3132
3233.. _Reno Documentation : https://docs.openstack.org/reno/latest/
3334
34- - As a quick example, when adding a new shell command for Awesome Storage Feature, one
35- could perform the following steps to include a release note for the new feature:
35+ - As a quick example, when adding a new shell command for Awesome Storage
36+ Feature, one could perform the following steps to include a release note for
37+ the new feature::
3638
3739 $ tox -e venv -- reno new add-awesome-command
3840 $ vi releasenotes/notes/add-awesome-command-bb8bb8bb8bb8bb81.yaml
3941
40- Remove the extra template text from the release note and update the details so it
41- looks something like:
42+ Remove the extra template text from the release note and update the details
43+ so it looks something like: :
4244
4345 ---
4446 features:
4547 - Added shell command `cinder be-awesome` for Awesome Storage Feature.
4648
47- - Include the generated release notes file when submitting your patch for review.
49+ - Include the generated release notes file when submitting your patch for
50+ review.
0 commit comments