r46930 - review comments

Author: hawkowl
Date: Sun Mar  6 22:46:48 2016
New Revision: 46930

Modified:
   branches/release-process-4543/docs/core/development/policy/release-process.rst

Log:
review comments

Modified: branches/release-process-4543/docs/core/development/policy/release-process.rst
==============================================================================
--- branches/release-process-4543/docs/core/development/policy/release-process.rst	(original)
+++ branches/release-process-4543/docs/core/development/policy/release-process.rst	Sun Mar  6 22:46:48 2016
@@ -177,7 +177,10 @@
 1. Have the release branch, previously used to generate a pre-release, checked out
 2. Run ``./bin/admin/change-versions``
 3. Add the quote of the release to the ``README``
-4. Make a new quote file for the next version: ``git mv docs/fun/Twisted.Quotes docs/historic/Quotes/Twisted-$API; echo '' > docs/fun/Twisted.Quotes; git add docs/fun/Twisted.Quotes``
+4. Make a new quote file for the next version
+
+   - ``git mv docs/fun/Twisted.Quotes docs/historic/Quotes/Twisted-$API; echo '' > docs/fun/Twisted.Quotes; git add docs/fun/Twisted.Quotes``
+
 5. Commit the version and ``README`` changes.
 6. Submit the ticket for review
 7. Pause until the ticket is reviewed and accepted.
@@ -380,7 +383,9 @@
 - How do we manage the case where there are untested builds in trunk?
 - Should picking a release quote be part of the release or the pre-release?
 - What bugs should be considered release blockers?
+
   - All bugs with a type from the release blocker family
   - Anybody can create/submit a new ticket with a release blocker type
   - Ultimately it's the RM's discretion to accept a ticket as a release blocker
+
 - Should news fragments contain information about who made the changes?