diff --git a/doc/bug-report.xml b/doc/bug-report.xml index 8a97bfbcd3b6e90999efadcb7397fd2e30f1e840..6205b5a848d6ebc5f5129d30d51332777593e969 100644 --- a/doc/bug-report.xml +++ b/doc/bug-report.xml @@ -4,8 +4,8 @@ <s1 title="Bug Reporting"> <s2 title="How to report bugs"> - <p> Please report bugs to <jump href="http://nagoya.apache.org/bugzilla/">Bugzilla</jump>, - the Apache bug database. Pick the product "Xerces-C++: Apache XML parsers in C++" + <p> Please report bugs to <jump href="http://nagoya.apache.org/jira">Jira</jump>, + the Apache bug database. Pick the product "Xerces-C++" using the following components: </p> <table> @@ -27,20 +27,15 @@ </s2> <s2 title="Search first"> - <p> Check the <jump href="http://nagoya.apache.org/bugzilla/">Bugzilla</jump> database + <p> Check the <jump href="http://nagoya.apache.org/jira">Jira</jump> database before submitting your bug report to avoid creating a duplicate report. Even the bug has been reported already, you may add a comment to the existing report since your contribution may lead to a quicker identification/resolution to the bug reported. </p> <p> Here is the list of <jump 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=Xerces-C%2B%2B&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.bug_id"> - outstanding bugs</jump> that are currently reported in Bugzilla. - </p> - <p> Here is the list of - <jump href= - "http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&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=Xerces-C%2B%2B&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=PatchAvailable&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&newqueryname=&order=bugs.bug_id"> - outstanding patch</jump>. + "http://nagoya.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10510&statusIds=1"> + outstanding bugs</jump> that are currently reported in Jira. </p> </s2> @@ -63,8 +58,6 @@ are all necessary information to allow developer to reproduce, identify, evaluate and eventually, fix the bug, which is the very purpose of your reporting of the bug. - </p> - <p> And please use the Keyword <code>"PatchAvailable"</code> if a patch is attached - </p> + </p> </s2> </s1> diff --git a/doc/build-misc.xml b/doc/build-misc.xml index 5fc361f667a5d44aba36ffd3fccea558c16d6a34..4750323f4962aced731407d86cf0d84aa838dca6 100644 --- a/doc/build-misc.xml +++ b/doc/build-misc.xml @@ -310,7 +310,7 @@ rpmbuild -ta &XercesCSrcInstallDir;.tar.gz (rpm 4.1 and later; ships with RedHat solved this same problem before you, by checking the Apache XML mailing list archives at <jump href="http://marc.theaimsgroup.com/?l=xerces-c-dev"> http://marc.theaimsgroup.com/?l=xerces-c-dev</jump> and the - <jump href="http://nagoya.apache.org/bugzilla/">Bugzilla</jump> + <jump href="http://nagoya.apache.org/jira">Jira</jump> Apache bug database.</p> </s2> diff --git a/doc/releases_plan.xml b/doc/releases_plan.xml index 4821c5b00e3dcf3b54f8a513a87aba88636334b6..522c26dd851c94f3eef371c352f55f291cf870ec 100644 --- a/doc/releases_plan.xml +++ b/doc/releases_plan.xml @@ -9,7 +9,7 @@ <s3 title="Next Target Release"><p>&XercesCName; 2.6.0 - plan to be released in the 4th quarter of 2004.</p></s3> <s3 title="&XercesCName; Features list"> <p> The following table lists the TODO items for &XercesCName; 2.6.0. It does not include fixing -bugs that are opened in Bugzilla; unless such Bugzilla bug involves a major development +bugs that are opened in Jira; unless such Jira bug involves a major development effort and requires an architectural redesign, or is an enhancement suggestion.</p> <table>