Use of Xalan-J versions in JIRA fields

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

Users/Developers:
it would be helpful if we kept the affect/fix version fields with correct
information
in JIRA issues.

"AFFECTS VERSIONS"  FIELD
===========================
After the Xalan-J 2.7 version was released on Aug 8, 2005, it became clear
to me
that it would be helpful if issue creators would fill in the "Affects
Version" field
with the version that they are reporting the problem against. Sometimes the
version information is in the text of the issue, but not marked in this
field.

For example, if you are using Xalan-J 2.6 and you find a problem in it
please open the issue against an affected version of "2.6". Of course it
might
be a problem in earlier or later versions too, and if you know you can
select multiple versions with control+mouse click rather than just mouse
click
to select multiple versions from the box.

"FIX VERSION" FIELD
===================
When developers resolve an issue, they should fill in the "Fix Version"
field,
which is the version that has the fix in it.

For example if you fix a problem reported against version 2.6, but you fix
it
in the current code base, please mark the fix version as "Latest
Development Code".
Xalan-J hasn't had a history of fixing problems in previously released
versions, so
99.9999% of the time "Latest Development Code" is the fix version to
select.



THE VERSIONS
===========
Be aware that the version previously named "currentCVS" was recently
renamed to "Latest Development Code", a more meaningful name. This is the
only version that does not have a corresponding Xalan-J release,
and it is marked as an unreleased version in JIRA. All other versions
were released as a product, and are marked as released.

When the next version of Xalan-J comes a long we'll probably create a new
released version (e.g. 2.7.1), and do a bulk change regarding the
fix version field. It could go something like this: all issues marked
as fixed against "Latest Development Code" will have their fix version
changed to that new released version. In this way it will be easy to query
which issues are resolved in that release.



I did some looking through the mailing lists and found these release dates
for these versions of Xalan-J

Latest Development Code - No date
2.7                     - 2005, August 8
2.6                     - 2004, February 29
2.5.2                   - 2003, October 30
2.5.1                   - 2003, June 3
2.5.0                   - 2003, April 4
2.4.1                   - 2002, October 31
2.4.0                   - 2002, September 3
2.3.1                   - 2002, February 21
2.3                     - 2002, February 14
2.2                     - 2002, January 16
2.1                     - 2001, May 23
2.0.4                   - ?
2.0.3                   - ?
2.0.2                   - ?
2.0.1                   - 2001, March 20
2.0.0                   - ? 2001, February 2 ?



- Brian
- - - - - - - - - - - - - - - - - - - -
Brian Minchau
Apache Xalan PMC Member