[Checkins] SVN: zopetoolkit/trunk/source/process/ * release critical bugs can block a release.

[Martijn Faassen]

Log message for revision 101426:
  * release critical bugs can block a release.
  
  * XXX comments and friends are *not* release blockers - file an
    issue instead.
  
  

Changed:
  U   zopetoolkit/trunk/source/process/bug-tracking.rst
  U   zopetoolkit/trunk/source/process/releasing-software.rst

-=-
Modified: zopetoolkit/trunk/source/process/bug-tracking.rst
===================================================================
--- zopetoolkit/trunk/source/process/bug-tracking.rst	2009-07-03 10:22:04 UTC (rev 101425)
+++ zopetoolkit/trunk/source/process/bug-tracking.rst	2009-07-03 10:22:14 UTC (rev 101426)
@@ -8,3 +8,10 @@
 http://www.zope.org/Collectors) have aliases of the form zope3dev-NNN where NNN
 is the old bug number, so they can be retrieved by searching for these on
 Launchpad.
+
+``XXX``, ``FIXME`` or ``TODO`` comments in the source code are not
+considered bugs and therefore cannot block releases. Consider adding a
+bug in addition to the comment. If something is really broken and you
+want to indicate it with ``XXX``, consider instead not checking this
+into the trunk of a project at all.
+

Modified: zopetoolkit/trunk/source/process/releasing-software.rst
===================================================================
--- zopetoolkit/trunk/source/process/releasing-software.rst	2009-07-03 10:22:04 UTC (rev 101425)
+++ zopetoolkit/trunk/source/process/releasing-software.rst	2009-07-03 10:22:14 UTC (rev 101426)
@@ -3,7 +3,9 @@
 
 When releasing software, the following steps should be taken:
 
-1. Make sure all automated tests of the package pass.
+1. Make sure all automated tests of the package pass. If the package
+   is tracking bugs on launchpad, make sure there are no release
+   critical bugs for that release.
 
 2. Fill in the release date in ``CHANGES.txt``.  Make sure the
    changelog is complete.