You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by Michael Glavassevich <mr...@ca.ibm.com> on 2004/05/01 00:11:18 UTC
RE: xerces components
"swapna gupta" <sw...@hotmail.com> wrote on 04/25/2004 04:07:31
AM:
> This is in reference to the earlier mail I sent about Xerces components.
>
> I understand the components listed in Bugzilla/Jira have no one-to-one
> relationship with the source packages/classes.
There also isn't a one-to-one relationship between Bugzilla/Jira reports
and actual bugs. We've had several bugs which have been reported multiple
times, like the schema location bug in Xerces 2.3.0 [1].
> But is there any way I can get bugs for at least one version of Xerces,
> classified per class basis, i.e. classified according to the classes
which
> had to be modified in order to fix the bug?
None that I know of. The association between reports in Bugzilla/Jira and
changes in CVS is pretty weak. When I commit a change which fixes a bug,
in the commit message I usually reference and/or link to the bug report.
Some of the other committers have followed this convention too.
> Swapna
[1] http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16528
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org