From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-403995-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 9354 invoked by alias); 18 Oct 2012 12:42:46 -0000
Received: (qmail 9313 invoked by uid 48); 18 Oct 2012 12:42:32 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/54973] New: [bugzilla] make "Before reporting a bug" notice more prominent
Date: Thu, 18 Oct 2012 12:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-54973-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2012-10/txt/msg01671.txt.bz2


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54973

             Bug #: 54973
           Summary: [bugzilla] make "Before reporting a bug" notice more
                    prominent
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: web
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: redi@gcc.gnu.org
                CC: LpSolit@netscape.net


The top of the Enter Bug page says:

"Before reporting a bug, please read the bug writing guidelines, please look at
the list of most frequently reported bugs, and please search for the bug."

with links to important pages describing the info needed in a bug report
(preprocessed source, output of "gcc -v" etc.) as well as suggesting checking
for compiler warnings before reporting a non-bug.

Many first-time bug reporters apparently don't read the guidelines because they
don't submit testcases, don't provide the compilation command, don't say which
compiler version they're using etc. which requires a maintainer to reply asking
for that info and set the bug to WAITING, wasting time and effort for the
reporter and maintainers.

I think the notice at the top of the page could be far more prominent, maybe it
could even duplicate some of the most important info from the top of the
http://gcc.gnu.org/bugs page.