You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by sl...@apache.org on 2002/04/29 18:56:34 UTC
cvs commit: httpd-site/docs bug_report.html
slive 02/04/29 09:56:34
Modified: xdocs bug_report.xml
docs bug_report.html
Log:
Give potential bug reporters a little more help in tracking down
old bugs to avoid duplicates.
Revision Changes Path
1.4 +109 -99 httpd-site/xdocs/bug_report.xml
Index: bug_report.xml
===================================================================
RCS file: /home/cvs/httpd-site/xdocs/bug_report.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -b -u -r1.3 -r1.4
--- bug_report.xml 16 Mar 2002 18:34:00 -0000 1.3
+++ bug_report.xml 29 Apr 2002 16:56:33 -0000 1.4
@@ -32,38 +32,48 @@
frustrating to take time and effort to track down a problem only
to figure out it caused by a broken third party module.
</li>
- <li>Checked the <A HREF="docs/misc/FAQ.html">FAQ</A>.
- </li>
- <li>Searched the <A HREF="http://nagoya.apache.org/bugzilla/">bug report</A>
- database. When you are doing this, you should be sure to search
- closed problem reports in addition to open ones. Also note that
- the search is not keyword based, so it requires an exact match
- of what you enter to find anything.
- </li>
<li>Looked at the error log. Please include any related messages in your
report, or state that there are none.
</li>
+ <li>Checked the <A HREF="docs/misc/FAQ.html">FAQ</A>.
+ </li>
+ <li>Searched the <A HREF="http://nagoya.apache.org/bugzilla/">bug
+ report</A> database. When you are doing this, you should be sure to
+ search closed problem reports in addition to open ones. The search
+ form on the main bugzilla page by default applies only to open
+ reports; to search all bug reports, begin the search with the keyword
+ "ALL". For example, the following search will find all reported
+ proxy bugs in Apache 2.0: "ALL httpd-2.0 mod_proxy". Some helpful
+ queries:
+ <ul>
+ <li><a
+ href="http://nagoya.apache.org/bugzilla/buglist.cgi?resolution=FIXED&changedin=60&product=Apache+httpd-1.3&product=Apache+httpd-2.0">All
+ bugs fixed in the last 60 days</a></li> <li><a
+ href="http://nagoya.apache.org/bugzilla/buglist.cgi?product=Apache+httpd-1.3&product=Apache+httpd-2.0&long_desc=duplicate+of+this+bug.&long_desc_type=allwordssubstr&changedin=30">Frequently
+ reported bugs</a> (bugs with duplicates changed in the last 30
+ days)</li> <li><a
+ href="http://nagoya.apache.org/bugzilla/buglist.cgi?changedin=10&product=Apache+httpd-1.3&product=Apache+httpd-2.0">All
+ bugs changed in the last 10 days</a></li>
+ </ul>
+ </li>
</ol>
<note>
- <strong>
- <p>If you're not sure that your problem is specifically related to a
- bug in Apache (<em>i.e.</em>, not something like a client problem or
- configuration problem), we strongly recommend that you check
- the <a href="userslist.html">Apache HTTP Server Users List</a>.
- If you don't
- receive a response within a few days, then please submit it to
- the Apache bug database. If it's a known issue, you'll probably
- get a faster response from the mailing list 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 mailing list.</p>
+ <p>Unless you are sure you have found a bug in the Apache HTTP
+ Server, we strongly recommend that you try the <a
+ href="userslist.html">Apache HTTP Server Users List</a> before using
+ the bug database. If you don't receive a response within a few
+ days, then please submit it to the Apache bug database. If it's a
+ known issue, you'll probably get a faster response from the mailing
+ list 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 mailing
+ list.</p>
<p>Do <strong>not</strong> post to the mailing list and submit a bug
report at the same time. This wastes everyone's time.
Post to the mailing list and wait a few days.
</p>
- </strong>
</note>
<p>If you have done all of the preceding, then please select the button
@@ -86,8 +96,8 @@
<p>Use the links below to submit bug reports:</p>
<ul>
<li><a href="http://nagoya.apache.org/bugzilla/">Apache Bug Database</a>.
-The appropriate Bugzilla projects for Apache HTTPD are "Apache HTTPD"
-(for 1.3) and "Apache HTTPD 2" (for 2.0).</li>
+The appropriate Bugzilla projects for Apache HTTPD are "Apache httpd-1.3"
+and "Apache httpd-2.0".</li>
<li><a href="http://bugs.apache.org/">Old Apache Bug Database</a>.
You may look at our old Apache Bug Database, but it will not be
kept up to date or maintained. Please submit new bugs to the
1.10 +29 -23 httpd-site/docs/bug_report.html
Index: bug_report.html
===================================================================
RCS file: /home/cvs/httpd-site/docs/bug_report.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -b -u -r1.9 -r1.10
--- bug_report.html 16 Mar 2002 18:34:00 -0000 1.9
+++ bug_report.html 29 Apr 2002 16:56:34 -0000 1.10
@@ -83,38 +83,44 @@
frustrating to take time and effort to track down a problem only
to figure out it caused by a broken third party module.
</li>
- <li>Checked the <A HREF="docs/misc/FAQ.html">FAQ</A>.
- </li>
- <li>Searched the <A HREF="http://nagoya.apache.org/bugzilla/">bug report</A>
- database. When you are doing this, you should be sure to search
- closed problem reports in addition to open ones. Also note that
- the search is not keyword based, so it requires an exact match
- of what you enter to find anything.
- </li>
<li>Looked at the error log. Please include any related messages in your
report, or state that there are none.
</li>
+ <li>Checked the <A HREF="docs/misc/FAQ.html">FAQ</A>.
+ </li>
+ <li>Searched the <A HREF="http://nagoya.apache.org/bugzilla/">bug
+ report</A> database. When you are doing this, you should be sure to
+ search closed problem reports in addition to open ones. The search
+ form on the main bugzilla page by default applies only to open
+ reports; to search all bug reports, begin the search with the keyword
+ "ALL". For example, the following search will find all reported
+ proxy bugs in Apache 2.0: "ALL httpd-2.0 mod_proxy". Some helpful
+ queries:
+ <ul>
+ <li><a href="http://nagoya.apache.org/bugzilla/buglist.cgi?resolution=FIXED&changedin=60&product=Apache+httpd-1.3&product=Apache+httpd-2.0">All
+ bugs fixed in the last 60 days</a></li> <li><a href="http://nagoya.apache.org/bugzilla/buglist.cgi?product=Apache+httpd-1.3&product=Apache+httpd-2.0&long_desc=duplicate+of+this+bug.&long_desc_type=allwordssubstr&changedin=30">Frequently
+ reported bugs</a> (bugs with duplicates changed in the last 30
+ days)</li> <li><a href="http://nagoya.apache.org/bugzilla/buglist.cgi?changedin=10&product=Apache+httpd-1.3&product=Apache+httpd-2.0">All
+ bugs changed in the last 10 days</a></li>
+ </ul>
+ </li>
</ol>
<table border="1" cellpadding="5"><tr><td>
<note>
- <strong>
- <p>If you're not sure that your problem is specifically related to a
- bug in Apache (<em>i.e.</em>, not something like a client problem or
- configuration problem), we strongly recommend that you check
- the <a href="userslist.html">Apache HTTP Server Users List</a>.
- If you don't
- receive a response within a few days, then please submit it to
- the Apache bug database. If it's a known issue, you'll probably
- get a faster response from the mailing list 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 mailing list.</p>
+ <p>Unless you are sure you have found a bug in the Apache HTTP
+ Server, we strongly recommend that you try the <a href="userslist.html">Apache HTTP Server Users List</a> before using
+ the bug database. If you don't receive a response within a few
+ days, then please submit it to the Apache bug database. If it's a
+ known issue, you'll probably get a faster response from the mailing
+ list 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 mailing
+ list.</p>
<p>Do <strong>not</strong> post to the mailing list and submit a bug
report at the same time. This wastes everyone's time.
Post to the mailing list and wait a few days.
</p>
- </strong>
</note>
</tr></td></table>
<p>If you have done all of the preceding, then please select the button
@@ -137,8 +143,8 @@
<p>Use the links below to submit bug reports:</p>
<ul>
<li><a href="http://nagoya.apache.org/bugzilla/">Apache Bug Database</a>.
-The appropriate Bugzilla projects for Apache HTTPD are "Apache HTTPD"
-(for 1.3) and "Apache HTTPD 2" (for 2.0).</li>
+The appropriate Bugzilla projects for Apache HTTPD are "Apache httpd-1.3"
+and "Apache httpd-2.0".</li>
<li><a href="http://bugs.apache.org/">Old Apache Bug Database</a>.
You may look at our old Apache Bug Database, but it will not be
kept up to date or maintained. Please submit new bugs to the