You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by ma...@hyperreal.org on 1998/03/25 06:05:14 UTC

cvs commit: apache-site bug_report.html

marc        98/03/24 21:05:14

  Modified:    .        bug_report.html
  Log:
  Let's shout even louder at people about submitting bug reports.
  
  Revision  Changes    Path
  1.9       +9 -3      apache-site/bug_report.html
  
  Index: bug_report.html
  ===================================================================
  RCS file: /export/home/cvs/apache-site/bug_report.html,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- bug_report.html	1997/11/08 23:29:59	1.8
  +++ bug_report.html	1998/03/25 05:05:13	1.9
  @@ -16,8 +16,8 @@
   
   <P>Welcome to the Apache Bug Reporting Page!  If you are having trouble
   with Apache, please fill out a problem report form and submit it.  
  -Before you do that, though, make <b>sure</b> you have done <b>all</b>
  -of the following:</P>
  +Before you do that, though, <FONT COLOR="red">make <b>sure</b> you have 
  +done <b>all</b> of the following:</FONT></P>
   
   <OL>
   <LI>Verified that the bug exists in <A href="mirrors/">the most recent version</A>
  @@ -33,7 +33,9 @@
       <code>Makefile</code>.
   <LI>Tried compiling with only the distributed set of modules and with
       no other patches (so that we can make sure it's an Apache bug and 
  -    not a bug in a module or patch provided by someone else).
  +    not a bug in a module or patch provided by someone else).  It is 
  +    frustrating to take time and effort to track down a problem only 
  +    to figure out it caused by a broken third party module.
   <LI>Checked the <A HREF="docs/misc/FAQ.html">FAQ</A>.
   <LI>Searched the <A HREF="http://www.apache.org/bugdb.cgi">bug report</A>
       database.  When you are doing this, you should be sure to search
  @@ -56,6 +58,10 @@
     and you will help keep developer time free for improving Apache.  Most
     bug reports submitted are actually user configuration problems that 
     could be easily fixed by asking in the newsgroup.
  +
  +  <P><FONT COLOR="red">Do <B>not</B> post to Usenet and submit a bug 
  +  report at the same time.</FONT>  This wastes everyone's time.  
  +  Post to Usenet and wait a few days.
    </STRONG>
   </BLOCKQUOTE>
   
  
  
  

Re: cvs commit: apache-site bug_report.html

Posted by Marc Slemko <ma...@worldgate.com>.
Since we have failed to get any more people to help with bug reports, we
have to try cutting down the number of reports.

I'm wondering if we have to add a hidden password in this and then make
people enter it to a form before they can submit a report.

I keep thinking that http://bugs.apache.org/ should really display this
junk, since we may have people just going there without seeing the other
one.

On 25 Mar 1998 marc@hyperreal.org wrote:

> marc        98/03/24 21:05:14
> 
>   Modified:    .        bug_report.html
>   Log:
>   Let's shout even louder at people about submitting bug reports.
>   
>   Revision  Changes    Path
>   1.9       +9 -3      apache-site/bug_report.html
>   
>   Index: bug_report.html
>   ===================================================================
>   RCS file: /export/home/cvs/apache-site/bug_report.html,v
>   retrieving revision 1.8
>   retrieving revision 1.9
>   diff -u -r1.8 -r1.9
>   --- bug_report.html	1997/11/08 23:29:59	1.8
>   +++ bug_report.html	1998/03/25 05:05:13	1.9
>   @@ -16,8 +16,8 @@
>    
>    <P>Welcome to the Apache Bug Reporting Page!  If you are having trouble
>    with Apache, please fill out a problem report form and submit it.  
>   -Before you do that, though, make <b>sure</b> you have done <b>all</b>
>   -of the following:</P>
>   +Before you do that, though, <FONT COLOR="red">make <b>sure</b> you have 
>   +done <b>all</b> of the following:</FONT></P>
>    
>    <OL>
>    <LI>Verified that the bug exists in <A href="mirrors/">the most recent version</A>
>   @@ -33,7 +33,9 @@
>        <code>Makefile</code>.
>    <LI>Tried compiling with only the distributed set of modules and with
>        no other patches (so that we can make sure it's an Apache bug and 
>   -    not a bug in a module or patch provided by someone else).
>   +    not a bug in a module or patch provided by someone else).  It is 
>   +    frustrating to take time and effort to track down a problem only 
>   +    to figure out it caused by a broken third party module.
>    <LI>Checked the <A HREF="docs/misc/FAQ.html">FAQ</A>.
>    <LI>Searched the <A HREF="http://www.apache.org/bugdb.cgi">bug report</A>
>        database.  When you are doing this, you should be sure to search
>   @@ -56,6 +58,10 @@
>      and you will help keep developer time free for improving Apache.  Most
>      bug reports submitted are actually user configuration problems that 
>      could be easily fixed by asking in the newsgroup.
>   +
>   +  <P><FONT COLOR="red">Do <B>not</B> post to Usenet and submit a bug 
>   +  report at the same time.</FONT>  This wastes everyone's time.  
>   +  Post to Usenet and wait a few days.
>     </STRONG>
>    </BLOCKQUOTE>
>    
>   
>   
>   
>