cvs commit: xml-fop/src/documentation/content/xdocs bugs.xml gethelp.xml resources.xml
vmote 2003/04/05 11:29:26 Modified:src/documentation/content/xdocs bugs.xml gethelp.xml resources.xml Log: Fix link to "Asking Questions ..." Normalize and clean up content. Revision ChangesPath 1.5 +8 -28 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.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- bugs.xml 15 Mar 2003 19:59:46 - 1.4 +++ bugs.xml 5 Apr 2003 19:29:26 - 1.5 @@ -30,40 +30,20 @@ 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 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, but please be sure to mark -the issue as an enhancement. - Is your issue addressed by an http://xml.apache.org/fop/faq.html";>FAQ? If so, please do not -enter a bug report unless the FAQ did not adequately address your issue. - 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 -http://nagoya.apache.org/bugzilla/bugwritinghelp.html";>Apache Bug -Writing Guidelines before submitting your report. - If, and only if, you have passed all of the above steps, please -enter a new bug report at -http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Fop";>The -FOP bug database (Bugzilla). +us track these issues down. + +To help us ensure that the bug database is as useful as it should be, please +use the Getting Help checklist to determine whether a bug report should be entered. +Review the http://nagoya.apache.org/bugzilla/bugwritinghelp.html";>Apache Bug Writing Guidelines before submitting your report. +Enter a new issue report at http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Fop";>The FOP issue database (Bugzilla). You will be asked to login to an existing Bugzilla account or to create a new one. When entering the bug report, please make your description complete and concise. If appropriate, attach a minimal fo file to your report which demonstrates the problem. - After submission, a copy of your bug report will be automatically +After submission, a copy of your bug report will be automatically sent to the FOP developer discussion list. - + - 1.4 +69 -63xml-fop/src/documentation/content/xdocs/gethelp.xml Index: gethelp.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/gethelp.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- gethelp.xml 14 Mar 2003 00:12:10 - 1.3 +++ gethelp.xml 5 Apr 2003 19:29:26 - 1.4 @@ -3,72 +3,78 @@ "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd";> -How to Get Help -Solving problems +Getting Help +Checklist for Finding Appropriate Resources +The FOP developer community is eager to help you maximize the usefulness of FOP. +However, to make wise use of its limited resources, support must be primarily self-service. +Go through the following checklist sequentially to determine what kind of help you need, +and where to get it: - How to get Help - - - Have a look at the documentation pages on this site. You can find - information on how to run FOP, how to embed it, how to add custom - fonts etc. - - - Consult the FAQ to see if your question - has already been answered before. - - - If you have a question concerning XSLFO that is not related to FOP - directly or regarding XSLT, please consult the various resources on - the net. See Resources for some - interesting links. - - - Before you post your questions to one of the mailing lists, please -
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 ChangesPath 1.4 +25 -16xml-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 - 1.3 +++ bugs.xml 15 Mar 2003 19:59:46 - 1.4 @@ -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 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). +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 http://xml.apache.org/fop/faq.html";>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 http://nagoya.apache.org/bugzilla/bugwritinghelp.html";>Apache Bug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs bugs.xml
keiron 2002/11/18 04:47:16 Modified:src/documentation/content/xdocs bugs.xml Log: better links to Bugzilla. reorganized content into a checklist. Submitted by: [EMAIL PROTECTED] (Victor Mote) Revision ChangesPath 1.2 +48 -15xml-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.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- bugs.xml 4 Nov 2002 16:20:51 - 1.1 +++ bugs.xml 18 Nov 2002 12:47:16 - 1.2 @@ -7,20 +7,53 @@ - How to report bugs -Please report bugs to http://nagoya.apache.org/bugzilla/";>bugzilla, the Apache bug - database. A copy of your bug report is sent automatically to the discussion list [EMAIL PROTECTED] -Please make sure, before you report a bug, that it is not mentioned in the FAQ or - in the list of open bugs at bugzilla. -Please make your description as concise as possible and add an example fo - file with your report, which just demonstrates the problem. Thanks for your help! - - -Known bugs -A list of known bugs can be found at - http://nagoya.apache.org/bugzilla/";>bugzilla. - - + Bugs Already Reported + A list of unresolved reported bugs can be found at +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). + + + Reporting New Bugs + 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: + + 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). + Is your issue addressed by an http://xml.apache.org/fop/faq.html";>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. + Do you know how to write a good bug report? +Please review the +http://nagoya.apache.org/bugzilla/bugwritinghelp.html";>Apache Bug +Writing Guidelines before submitting your report. + If, and only if, you have passed all of the above steps, please +enter a new bug report at +http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Fop";>The +FOP bug database (Bugzilla). +You will be asked to login to an existing Bugzilla account or to create a new +one. +When entering the bug report, please make your description complete and concise. +If appropriate, attach a minimal fo file to your report which demonstrates the +problem. + After submission, a copy of your bug report will be automatically +sent to the FOP developer discussion list. + + + - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
