This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
[www-patch] bugs/management.html: Clarify how to handle regressions
- From: Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>
- To: gcc-patches at gcc dot gnu dot org
- Cc: gcc at gcc dot gnu dot org, mark at codesourcery dot com, giovannibajo at libero dot it,bangerth at ices dot utexas dot edu, charlet at ACT-Europe dot FR,S dot Bosscher at student dot tudelft dot nl, gdr at integrable-solutions dot net,nathan at codesourcery dot com
- Date: Tue, 13 Jan 2004 00:10:47 +0100 (CET)
- Subject: [www-patch] bugs/management.html: Clarify how to handle regressions
- Reply-to: Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>
The following patch clarifies the paragraph how to handle regressions
in bugs/management.html. For a discussion of the subject see
http://gcc.gnu.org/ml/gcc/2004-01/msg00716.html
Does everybody agree with this policy?
Checked as valid XHTML 1.0.
Ok to commit?
Regards,
Volker
Index: management.html
===================================================================
RCS file: /home/reichelt/GCC/CVS/gcc-cvs/wwwdocs/htdocs/bugs/management.html,v
retrieving revision 1.21
diff -c -p -r1.21 management.html
*** management.html 20 Oct 2003 11:04:18 -0000 1.21
--- management.html 12 Jan 2004 23:00:10 -0000
*************** marked as such. The summary line should
*** 200,211 ****
[<em>branches-to-fix</em> regression] <em>rest-of-summary</em>
</blockquote>
! <p>where <em>branches-to-fix</em> is the list of maintained
! branches (separated by slashes) that need fixing. In addition the target
! milestone should be set accordingly. A regression should start with
severity "<strong>critical</strong>" to bring it to attention. It may
be downgraded later if a defect is not important enough to justify
! "critical" severity.</p>
<p><strong>Meta-bugs (reports with the keyword "meta-bug")</strong> are
used to group PRs that have a common denominator. Meta-bugs do not have
--- 200,212 ----
[<em>branches-to-fix</em> regression] <em>rest-of-summary</em>
</blockquote>
! <p>where <em>branches-to-fix</em> is the list of maintained branches
! (separated by slashes) that need fixing. A regression should start with
severity "<strong>critical</strong>" to bring it to attention. It may
be downgraded later if a defect is not important enough to justify
! "critical" severity. In addition the target milestone should be set
! to the next release that needs fixing. The milestone can be changed
! by the release manager and his/her delegates.</p>
<p><strong>Meta-bugs (reports with the keyword "meta-bug")</strong> are
used to group PRs that have a common denominator. Meta-bugs do not have
===================================================================