This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [www] Policy for marking regressions in GNATS
- From: Janis Johnson <janis187 at us dot ibm dot com>
- To: Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>
- Cc: gcc-patches at gcc dot gnu dot org, pfeifer at dbai dot tuwien dot ac dot at
- Date: Wed, 18 Dec 2002 15:26:30 -0800
- Subject: Re: [www] Policy for marking regressions in GNATS
- References: <200212051455.PAA39824@numa6.igpm.rwth-aachen.de>
On Thu, Dec 05, 2002 at 03:55:12PM +0100, Volker Reichelt wrote:
> Policy for marking regressions in GNATS (for the new section
> "Procedures and Policies" in gnatswrite.html):
>
> (checked with validator.w3.org)
>
> ==============================================================================
> --- old/gnatswrite.html Tue Dec 5 14:14:15 2002
> +++ new/gnatswrite.html Tue Dec 5 14:30:21 2002
> @@ -156,6 +156,19 @@ report her findings in any case (whether
> <li>if no response arrives, close the PR after three months.</li>
> </ul>
>
> +<p><strong>Regressions</strong> should be explicitly marked as such.
> +The synopsis line should read</p>
> +
> +<blockquote>
> +[<branches-to-fix> regression] <rest-of-synopsis>
> +</blockquote>
> +
> +<p>where <branches-to-fix> is the list of <em>maintained</em>
> +branches (separated by slashes) that need fixing. A regression should
> +start with priority "<strong>high</strong>" to bring it to attention.
> +It may be downgraded later if a defect is not important enough to justify
> +"high priority".</p>
> +
>
>
>
> ==============================================================================
>
> OK?
Thanks, this is in now (sorry I didn't notice it sooner).
Janis