You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

bugs.xml 3.7KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667
  1. <?xml version="1.0" standalone="no"?>
  2. <!--
  3. Licensed to the Apache Software Foundation (ASF) under one or more
  4. contributor license agreements. See the NOTICE file distributed with
  5. this work for additional information regarding copyright ownership.
  6. The ASF licenses this file to You under the Apache License, Version 2.0
  7. (the "License"); you may not use this file except in compliance with
  8. the License. You may obtain a copy of the License at
  9. http://www.apache.org/licenses/LICENSE-2.0
  10. Unless required by applicable law or agreed to in writing, software
  11. distributed under the License is distributed on an "AS IS" BASIS,
  12. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  13. See the License for the specific language governing permissions and
  14. limitations under the License.
  15. -->
  16. <!-- $Id$ -->
  17. <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
  18. "http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/schema/dtd/document-v12.dtd?view=co">
  19. <document>
  20. <header>
  21. <title>FOP: Bugs and Other Trackable Issues</title>
  22. <version>$Revision$</version>
  23. </header>
  24. <body>
  25. <p>
  26. Information on this page applies to enhancement requests and other trackable
  27. issues as well as bugs.
  28. </p>
  29. <section id="issues_existing">
  30. <title>Reported Issues</title>
  31. <p>A list of unresolved reported bugs can be found at
  32. <link href="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;email1=&amp;emailtype1=substring&amp;emailassigned_to1=1&amp;email2=&amp;emailtype2=substring&amp;emailreporter2=1&amp;bugidtype=include&amp;bug_id=&amp;changedin=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;product=Fop&amp;short_desc=&amp;short_desc_type=allwordssubstr&amp;long_desc=&amp;long_desc_type=allwordssubstr&amp;bug_file_loc=&amp;bug_file_loc_type=allwordssubstr&amp;keywords=&amp;keywords_type=anywords&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">FOP
  33. Open Bugs (Bugzilla)</link>. If you have an interest in an issue already
  34. reported, please consider the following:
  35. </p>
  36. <ul>
  37. <li>If you have insight that may help developers solve an existing problem,
  38. please add comments and/or file attachments to the existing issue.</li>
  39. <li>If you would like to track the status of the issue, consider adding
  40. your email address to the list of "CC" recipients, so that you will receive
  41. an email as changes are made to the issue.</li>
  42. </ul>
  43. </section>
  44. <section id="issues_new">
  45. <title>Unreported Issues (Reporting New Issues)</title>
  46. <p>User reports of bugs and requests for enhancements are extremely
  47. important parts of FOP development, and we appreciate the time you take to help
  48. us track these issues down.</p>
  49. <ul>
  50. <li>To help us ensure that the bug database is as useful as it should be, please
  51. use the <link href="gethelp.html">Getting Help</link> checklist to determine whether a bug report should be entered.</li>
  52. <li>Review the <link href="http://issues.apache.org/bugzilla/page.cgi?id=bug-writing.html">Apache Bug Writing Guidelines</link> before submitting your report.</li>
  53. <li>Enter a new issue report at <link href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Fop">The FOP issue database (Bugzilla)</link>.
  54. You will be asked to login to an existing Bugzilla account or to create a new
  55. one.
  56. When entering the bug report, please make your description complete and concise.
  57. If appropriate, attach a minimal fo file to your report which demonstrates the
  58. problem.</li>
  59. <li>After submission, a copy of your bug report will be automatically
  60. sent to the FOP developer discussion list.</li>
  61. </ul>
  62. </section>
  63. </body>
  64. </document>