You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-commits@xmlgraphics.apache.org by vm...@apache.org on 2003/03/15 20:59:46 UTC
cvs commit: xml-fop/src/documentation/content/xdocs bugs.xml
vmote 2003/03/15 11:59:46
Modified: src/documentation/content/xdocs bugs.xml
Log:
make terminology more general to "issues" instead of just bugs.
clean up & normalize content a bit.
Revision Changes Path
1.4 +25 -16 xml-fop/src/documentation/content/xdocs/bugs.xml
Index: bugs.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/bugs.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- bugs.xml 19 Nov 2002 07:57:27 -0000 1.3
+++ bugs.xml 15 Mar 2003 19:59:46 -0000 1.4
@@ -4,40 +4,49 @@
<document>
<header>
- <title>Bugs</title>
+ <title>Bugs and Other Trackable Issues</title>
</header>
<body>
- <section>
- <title>Bugs Already Reported</title>
+ <p>
+ Information on this page applies to enhancement requests and other trackable
+issues as well as bugs.
+ </p>
+ <section id="issues_existing">
+ <title>Reported Issues</title>
<p>A list of unresolved reported bugs can be found at
<link href="http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Fop&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=bugs.component">FOP
-Open Bugs (Bugzilla)</link>.</p>
+Open Bugs (Bugzilla)</link>. If you have an interest in an issue already
+reported, please consider the following:
+ </p>
+ <ul>
+ <li>If you have insight that may help developers solve an existing problem,
+please add comments and/or file attachments to the existing issue.</li>
+ <li>If you would like to track the status of the issue, consider adding
+your email address to the list of "CC" recipients, so that you will receive
+an email as changes are made to the issue.</li>
+ </ul>
</section>
- <section>
- <title>Reporting New Bugs</title>
+ <section id="issues_new">
+ <title>Unreported Issues (Reporting New Issues)</title>
<p>User reports of bugs and requests for enhancements are extremely
important parts of FOP development, and we appreciate the time you take to help
us track these issues down.
To help us ensure that the bug database is as useful as it should be, please
-use the following checklist if you are considering reporting a new bug:</p>
+use the following checklist if you are considering reporting a new issue:</p>
<ul>
<li>Is your issue really a request to comply with some aspect of the
XSL-FO standard?
If so, please do not enter a bug report.
The developers already carefully track which standard requirements have been
implemented.
-Other enhancement requests are welcome (although they are not technically
-"bugs", they are entered and tracked in the same system -- just be sure to mark
-the issue as an enhancement).</li>
+Other enhancement requests are welcome, but please be sure to mark
+the issue as an enhancement.</li>
<li>Is your issue addressed by an <link
href="http://xml.apache.org/fop/faq.html">FAQ</link>? If so, please do not
enter a bug report unless the FAQ did not adequately address your issue.</li>
- <li>Has this bug already been reported?
-See section above for a list of bugs that have already been reported.
-If the bug has already been reported, please do not open a new bug report.
-Reporting the same bug twice will only slow the development team down.
-However, if you have insight that may help developers track an existing problem,
-please add comments and/or file attachments to the existing bug.</li>
+ <li>Has this issue already been reported? If so, please do not
+report it again, as this will only slow the development team down.
+See section above for a list of issues that have already been reported.</li>
<li>Do you know how to write a good bug report?
Please review the
<link href="http://nagoya.apache.org/bugzilla/bugwritinghelp.html">Apache Bug
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-cvs-help@xml.apache.org