mrglavas 2004/04/15 08:29:42
Modified: java/docs bugzilla.xml
Log:
Update docs on bug reporting to reflect recent
migration from Bugzilla to Jira.
Revision Changes Path
1.4 +10 -10 xml-xerces/java/docs/bugzilla.xml
Index: bugzilla.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/bugzilla.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- bugzilla.xml 25 Feb 2004 16:22:44 -0000 1.3
+++ bugzilla.xml 15 Apr 2004 15:29:42 -0000 1.4
@@ -15,7 +15,7 @@
* limitations under the License.
-->
<!DOCTYPE s1 SYSTEM "./dtd/document.dtd">
-<s1 title="Reporting Bugs in Bugzilla">
+<s1 title="Reporting Bugs in Jira">
<s2 title="Before you report a bug">
<p> Before you report a bug, please, <em>read</em> the following instructions:</p>
<ul>
@@ -24,28 +24,28 @@
xerces-j-user</jump> list for clarification.
</li>
<li>To help to eliminate duplicate or invalid bug reports, such as the
- <jump
href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16528";>external-schemaLocation</jump>
bug,
- <em>please take a quick look at bugs in Bugzilla</em> opened against the
version you're working
+ <jump
href="http://nagoya.apache.org/jira/browse/XERCESJ-581";>external-schemaLocation</jump>
bug,
+ <em>please take a quick look at bugs in Jira</em> opened against the
version you're working
with to see whether the bug has been already reported and/or fixed.
You can also download the
<jump href='http://gump.covalent.net/jars/latest/xml-xerces2/'>latest
code</jump>
in CVS and check if you can reproduce the bug.</li>
<li>Report bugs against the newest release.</li>
- <li>Read <jump href="http://nagoya.apache.org/bugzilla/";>Bugzilla
Notes</jump></li>
+ <li>Read <jump href="http://nagoya.apache.org/jira";>Jira Notes</jump></li>
</ul>
<p>We strongly encourage you write patches for problems you find and submit
- them to [EMAIL PROTECTED] Being specific in the description of your bug
report, and
- providing enough information to reproduce the bug will improve the
likelihood that the bug
- you found will be fixed in the foreseeable future. In the interest of
fixing bugs, adding
- enhancements, and addressing outstanding design issues, we need your
active participation in the
- ongoing development of Xerces2.</p>
+ them to <jump href="http://xml.apache.org/mail.html#xerces-j-dev";>[EMAIL
PROTECTED]</jump>.
+ Being specific in the description of your bug report, and providing enough
information to reproduce the
+ bug will improve the likelihood that the bug you found will be fixed in
the foreseeable future. In the
+ interest of fixing bugs, adding enhancements, and addressing outstanding
design issues, we need your
+ active participation in the ongoing development of Xerces2.</p>
<anchor name="bugzilla"/>
</s2>
<s2 title="Report a bug">
<p> Have you read the instructions above?
-If yes, please click <jump
href="http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Xerces2-J";>here</jump>
+If yes, please click <jump
href="http://nagoya.apache.org/jira/browse/XERCESJ";>here</jump>
to submit a bug report. </p>
</s2>
</s1>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
