Important: Starting immediately XalanJ2 and XalanC are no longer using Bugzilla!

[Brian Minchau <mi...@ca.ibm.com>]

 XalanJ2 and XalanC are now using JIRA for bug and issue tracking.
Bugzilla is no longer being used.

 To use JIRA go to http://nagoya.apache.org/jira/secure/Dashboard.jspa, or
to http://nagoya.apache.org/jira which will redirect you to the dashboard.

If you have ever created, commented on, or otherwise manipulated a XalanC
or XalanJ2 bugzilla bug, you should have your JIRA account already setup.
Your username and password should be a copy of your bugzilla username and
password.  The JIRA accounts are separate from bugzilla, but are just set
up the way they are for you to do an easy transition to JIRA.

Everyone can view public JIRA issues, and everyone with a JIRA account can
create or comment on Xalan issues in JIRA.  Active Xalan committers (from a
CVS point of view) have been given more authority, they can manage issues,
such as changing their status to fixed.  If you are a Xalan committer and
you think this isn't working for you, please sent me a note.

Existing bugzilla bugs for XalanC and XalanJ2 have been migrated or copied
to JIRA, but the numbers are not the same.  For example the most recent
XalanJ2 defect is numbered  31000, and its issue key in JIRA is
XALANJ-1934.

No new defects can be opened for XalanC or XalanJ2 in bugzilla; new defects
must be created in JIRA. However comments could be added to existing
bugzilla bugs, and this would not be reflected to the copies that JIRA has.
Likewise changes to the JIRA issues which are copies of the bugzilla bugs
will not be reflected back in bugzilla.

PLEASE stop using bugzilla immediately.

Brian Minchau
Xalan JIRA administrator
e-mail:        minchau@ca.ibm.com