No JIRA needed for CR bugfix

We discussed at the maintainers summit that we could simplify the CR processfor simple bug fixes by not requiring a JiRA be opened. This change to the process is documented in the section on reporting bugs. Signed-off-by: Christopher Ferris <[email protected]> Change-Id: I537eae68dbf850fd3ebc3c38596ac1c9641481d8
seuzht · Oct 11, 2019 · a75ae17 · a75ae17
1 parent c927adc
commit a75ae17
Showing 1 changed file with 3 additions and 1 deletion.
diff --git a/docs/source/CONTRIBUTING.rst b/docs/source/CONTRIBUTING.rst
@@ -218,7 +218,9 @@ the defect fixed.
 .. note:: If the defect is security-related, please follow the Hyperledger
           `security bug reporting process <https://wiki.hyperledger.org/display/HYP/Defect+Response>`__.
 
-If it has not been previously reported, create a new JIRA. Please try to provide
+If it has not been previously reported, you may either submit a CR with a
+well documented commit message describing the defect and the fix, or you 
+may create a new JIRA. Please try to provide
 sufficient information for someone else to reproduce the
 issue. One of the project's maintainers should respond to your issue within 24
 hours. If not, please bump the issue with a comment and request that it be