httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wr...@apache.org
Subject cvs commit: httpd-site/xdocs bug_report.xml
Date Tue, 01 Apr 2003 16:58:11 GMT
wrowe       2003/04/01 08:58:11

  Modified:    xdocs    bug_report.xml
  Log:
    Whitespace fix (not mine for a change)
  
  Revision  Changes    Path
  1.7       +109 -109  httpd-site/xdocs/bug_report.xml
  
  Index: bug_report.xml
  ===================================================================
  RCS file: /home/cvs/httpd-site/xdocs/bug_report.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- bug_report.xml	28 Dec 2002 21:15:53 -0000	1.6
  +++ bug_report.xml	1 Apr 2003 16:58:11 -0000	1.7
  @@ -1,115 +1,115 @@
  -<?xml version="1.0"?>
  -<document>
  -  <properties>
  -    <title>Bug Reporting</title>
  -  </properties>
  -<body>
  -<section>
  -<title>Bug Reporting</title>
  -
  -<note>
  -<strong>Reports of security issues should <em>not</em> be reported here.
  -Please see the <a href="security_report.html">security report page</a>
  -if you have concerns or think you have discovered a security hole in
  -the Apache Web server software.</strong>
  -</note>
  -
  -<p>If you have identified a bug in the Apache HTTP Server,
  -please fill out a problem report form and submit it.  
  -Before you do that, though, <font color="red">make <strong>sure</strong>
you
  -have done <strong>all</strong> of the following:</font></p>
  -
  -<ol>
  - <li>Verified that the bug exists in
  -  <a href="/download.cgi">the most recent version</a>
  -  of Apache.
  - </li>
  - <li>Followed the instructions in the <code>INSTALL</code> file correctly
  - </li>
  - <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).  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>
  - <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&amp;changedin=60&amp;product=Apache+httpd-1.3&amp;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&amp;product=Apache+httpd-2.0&amp;long_desc=duplicate+of+this+bug.&amp;long_desc_type=allwordssubstr&amp;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&amp;product=Apache+httpd-1.3&amp;product=Apache+httpd-2.0">All
  -  bugs changed in the last 10 days</a></li>
  -  </ul>
  - </li>
  -</ol>
  -
  -<note>
  -  <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>
  -</note>
  -
  -<p>If you have done all of the preceding, then please select the button
  -below and fill out the form, and we will respond to it as soon as we can.
  -</p>
  -
  -<note>
  -<ul>
  +<?xml version="1.0"?>
  +<document>
  +  <properties>
  +    <title>Bug Reporting</title>
  +  </properties>
  +<body>
  +<section>
  +<title>Bug Reporting</title>
  +
  +<note>
  +<strong>Reports of security issues should <em>not</em> be reported here.
  +Please see the <a href="security_report.html">security report page</a>
  +if you have concerns or think you have discovered a security hole in
  +the Apache Web server software.</strong>
  +</note>
  +
  +<p>If you have identified a bug in the Apache HTTP Server,
  +please fill out a problem report form and submit it.  
  +Before you do that, though, <font color="red">make <strong>sure</strong>
you
  +have done <strong>all</strong> of the following:</font></p>
  +
  +<ol>
  + <li>Verified that the bug exists in
  +  <a href="/download.cgi">the most recent version</a>
  +  of Apache.
  + </li>
  + <li>Followed the instructions in the <code>INSTALL</code> file correctly
  + </li>
  + <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).  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>
  + <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&amp;changedin=60&amp;product=Apache+httpd-1.3&amp;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&amp;product=Apache+httpd-2.0&amp;long_desc=duplicate+of+this+bug.&amp;long_desc_type=allwordssubstr&amp;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&amp;product=Apache+httpd-1.3&amp;product=Apache+httpd-2.0">All
  +  bugs changed in the last 10 days</a></li>
  +  </ul>
  + </li>
  +</ol>
  +
  +<note>
  +  <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>
  +</note>
  +
  +<p>If you have done all of the preceding, then please select the button
  +below and fill out the form, and we will respond to it as soon as we can.
  +</p>
  +
  +<note>
  +<ul>
    <li>
     <strong>
  -  Do NOT send configuration questions or requests for help debugging CGI!
  +  Do NOT send configuration questions or requests for help debugging CGI!
     </strong>
  - </li>
  + </li>
    <li>
     <strong>
  -  If you're tracing spam or you're here because one of your favourite Web
  -  sites now says 'It Worked! Apache is installed!' -- then contact the
  -  mail originator or the Web site's Webmaster directly, because they're
  -  just using our software and we have nothing to do with them.  Don't
  -  waste your time or ours by telling us about it.
  +  If you're tracing spam or you're here because one of your favourite Web
  +  sites now says 'It Worked! Apache is installed!' -- then contact the
  +  mail originator or the Web site's Webmaster directly, because they're
  +  just using our software and we have nothing to do with them.  Don't
  +  waste your time or ours by telling us about it.
     </strong>
  - </li>
  -</ul>
  -</note>
  -
  -<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-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
  -Bugzilla database.</li>
  -</ul>
  -
  -</section>
  -</body>
  -</document>
  + </li>
  +</ul>
  +</note>
  +
  +<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-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
  +Bugzilla database.</li>
  +</ul>
  +
  +</section>
  +</body>
  +</document>
  
  
  

Mime
View raw message