This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[www-patch] bugs/management.html: simplify generating release notes
- From: Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>
- To: gcc-patches at gcc dot gnu dot org
- Date: Tue, 14 Oct 2003 02:56:01 +0200 (CEST)
- Subject: [www-patch] bugs/management.html: simplify generating release notes
- Reply-to: Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>
To support Joe in his effort to generate the release notes, I'd like
to add the following two paragraphs to the "Procedures an Policies"
section of bugs/management.html.
Validated as XHTML 1.0.
Ok to commit?
Regards,
Volker
Index: management.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/management.html,v
retrieving revision 1.18
diff -u -p -r1.18 management.html
--- management.html 5 Oct 2003 12:54:35 -0000 1.18
+++ management.html 14 Oct 2003 00:07:50 -0000
@@ -228,6 +228,17 @@ report her findings in any case (whether
information that is necessary for reproducing the problem can be closed
if no response was received for three months.</p>
+<p><strong>When closing a PR</strong> because it got fixed, please
+set the <strong>target milestone</strong> to the first release where
+it will be fixed. Please adjust the target milestone when a fix is
+<strong>backported</strong>. This simplifies generating the release
+notes.</p>
+
+<p><strong>Duplicate PR's</strong> should be marked as such. If you
+encounter a PR that is marked as "resolved fixed", but should be marked
+as a duplicate, please change the resolution. (You have to reopen the
+PR before you can resolve it as a duplicate.) Again, this simplifies
+generating the release notes.</p>
</body>
</html>
===================================================================