PATCH for Re: PRs in category "bootstrap"

[Gerald Pfeifer]

On Tue, 19 Nov 2002, Mark Mitchell wrote:
>> Mark, does this sounds sensible?
> Eminently.

Great.  I believe we should document this kind of policies and procedures
(not the least for new contributors), so I went ahead an started a new
section in our documentation:

  Add a new section "Procedures and Policies" with an entry on "Bugs in
  category 'bootstrap'".

If you (Mark, Wolfgang,...) are aware of any further policies we should
document, please just go ahead, or let Janis and me know and we'll take
care of it.

Gerald

Index: gnatswrite.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gnatswrite.html,v
retrieving revision 1.11
diff -u -3 -p -r1.11 gnatswrite.html
--- gnatswrite.html	19 Jan 2002 12:48:33 -0000	1.11
+++ gnatswrite.html	21 Nov 2002 10:26:58 -0000
@@ -93,5 +93,18 @@ rather than suspended.</dd>
 GCC, indicating that a certain problem must be solved before the next
 version of GCC is released.</p>

+<h2>Procedures and Policies</h2>
+
+<p><strong>Bugs in category "bootstrap"</strong> that refer to older
+releases or snapshots/CVS versions should be put into state "feedback",
+asking the reporter whether she can still reproduce the problem and to
+report her findings in any case (whether positive or negative).</p>
+
+<ul>
+<li>If the response is "works now", close the report,</li>
+<li>if the reponse is "still broken", change the state to "open", and</li>
+<li>if no response arrives close the PR after three months.</li>
+</ul>
+
 </body>
 </html>