From 9a4051c084d3f61f7a491b87139b68c6eb173a47 Mon Sep 17 00:00:00 2001 From: William Victor Mote Date: Sat, 15 Mar 2003 19:59:46 +0000 Subject: [PATCH] make terminology more general to "issues" instead of just bugs. clean up & normalize content a bit. git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@196108 13f79535-47bb-0310-9956-ffa450edef68 --- src/documentation/content/xdocs/bugs.xml | 41 +++++++++++++++--------- 1 file changed, 25 insertions(+), 16 deletions(-) diff --git a/src/documentation/content/xdocs/bugs.xml b/src/documentation/content/xdocs/bugs.xml index c127b0048..8effa92e4 100644 --- a/src/documentation/content/xdocs/bugs.xml +++ b/src/documentation/content/xdocs/bugs.xml @@ -4,40 +4,49 @@
- Bugs + Bugs and Other Trackable Issues
-
- Bugs Already Reported +

+ Information on this page applies to enhancement requests and other trackable +issues as well as bugs. +

+
+ Reported Issues

A list of unresolved reported bugs can be found at FOP -Open Bugs (Bugzilla).

+Open Bugs (Bugzilla). If you have an interest in an issue already +reported, please consider the following: +

+
    +
  • If you have insight that may help developers solve an existing problem, +please add comments and/or file attachments to the existing issue.
    • +
  • 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.
    • +
-
- Reporting New Bugs +
+ Unreported Issues (Reporting New Issues)

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:

+use the following checklist if you are considering reporting a new issue:

  • 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).
    • +Other enhancement requests are welcome, but please be sure to mark +the issue as an enhancement.
  • Is your issue addressed by an FAQ? If so, please do not enter a bug report unless the FAQ did not adequately address your issue.
    • -
  • 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.
    • +
  • 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.
  • Do you know how to write a good bug report? Please review the Apache Bug -- 2.39.5