From ba33c20a24d3a29b4ae6aff34f314220dcbf4144 Mon Sep 17 00:00:00 2001 From: Graham Percival Date: Sun, 22 Nov 2009 20:20:11 +0000 Subject: [PATCH] Doc: CG: add another duty for bug meister. --- Documentation/contributor/issues.itexi | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi index 1796ff570b..2174812f17 100644 --- 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. + -- 2.39.5