Doc: CG: add another duty for bug meister.

diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi
index 1796ff570b6569567d7b684ea051fde5e8459db0..2174812f17a490ce26c507badf33607d82cdaad8 100644 (file)
--- a/Documentation/contributor/issues.itexi
+++ b/Documentation/contributor/issues.itexi
@@ -7,6 +7,7 @@
 * Issue classification::        
 * Adding issues to the tracker::  
 * Checking regression tests::
+* Checking old issues::
 @end menu
 
 
@@ -165,3 +166,17 @@ occasionally a bug will slip through the cracks.  It is therefore good to
 manually compare all the regtests twice a year or so.
 
 
+
+@node Checking old issues
+@section Checking old issues
+
+We try to mark each Issue @q{fixed} when we fix it, but
+occasionally one or two issues will slip through the cracks.
+Also, sometimes the Bug Meister will forget to verify that an
+issue has been fixed.
+
+It is therefore good to check all Issues once every 18 months or
+so.  If you see the same (broken) output as the initial report,
+then simply post a "Problem still exists in 2.x.y" message to the
+issue.
+