Subject:
Xalan-J bug triage minutes
Date:
Tuesday April 5, 2005
Xalan-J committers present:
- Brian Minchau (meeting chairperson)
- Dave Marston
- Henry Zongaro
- Joanne Tong
- John Gentilin
- Morris Kwan
- Sarah McNamara
- Yash Talwar
==================================================================================
1. Old Business
a) In the last meeting this issues were covered: 2067 back through 2052
b) In previous meetings issues covered: 2051 back through 2032
c) INFRA-233 was opened, the "User Picker" option of JIRA is unreliable
(bug was seen by Brian M. and John G.)
d) Had decided "resolving" issues that have no reply with 30 days
(the issue creator can always re-open). This was ratified by the PMC
recently.
e) Decided that resolved, rather than "closed" is good enough for Xalan-J
to consider the issue as not active. The issue creator should verify
the fix and close the issue. The fix could be in a patch, or as part
of a new Xalan release. So, in general, Xalan committers should not
close issues unless they themselves are the issue creator.
==================================================================================
2. The following XALANJ issues, opened since the March 1 meeting,
were addressed during the meeting:
2092 - added comment on XSLT 2.0 error XTSE0650, missing named template
probably won't fix
2088 - accepted as a request, not assigned.
2087 - assigned to Brian M.(asked Santiago P-G to look into, it is a Sun
class)
2086 - asked Santiago P-G to look into this as it is a Sun class, set to
fp4.
2084 - assigned to Brian M., will make this error a warning not an
exception.
2083 - agreed to give more time for a testcase.
2080 - Henry Z. to answer as won't fix.
2076 - assigned to Morris K.
2075 - resolved as invalid, but opened 2093 as a feature to add an API to
the serializer to set the line separator characters.
2073 - JBoss, probably class loader, added a comment, will probably resolve
as
invalid soon
2072 - assigned to Yash T. and Christine L.
2071 - note sent to Santiago P-G/Ramesh to ask if they would accept
assignement
2069 - assigned to Henry Z.
2067 - looks like a legitimate bug, no volunteer to assign to
2060 - already resolved
2052 - sound like old 1844 problem, waiting for response, resolving as
"Cannot Reproduce"
2046 - resolved as invalid
2086 - assigned to Brian M. to review the patch.
2078 - assigned to Yash Talwar, asked creator for modified patch
2077 - Henry Z. to review
==================================================================================
3. Round Table discussion
a) when you specify a "Fix Version" for an issue you can get a report of
what
things are fixed in bug report, the versions can be managed in a way
that
the Xalan custom field "target-release" is obsolete and should be
deleted.
b) will be removing sun.io.CharToByte converter from use in Xalan, but need
an alternate. This is covered in XALANJ-2087
c) John Gentilin has code from a Xalan user regarding SQL extensions.
The code is to use JNDI connections as a fallback if they are not in the
default
connection pool. John has taken the code, reviewed it,
made some modifications to it. Once the contributor signs the CLA John
will open a JIRA issue, attach the modified code to the issue, giving
the
contributor credit. Even though the code isn't exactly the same it is
considered
reviewed, so John can record his approval in the issue, and commit the
code.
==================================================================================
4. Review "blocker" or "critical" issues that are "unresolved"
1978 - assigned to Henry Z.
1934 - resolved as duplicate of 1955
1912 - comments added about Java equivalent of Lex,
requesting Santiago P-G to take this one, but didn't assign it to
him yet.
1574 - assigned to John G.
1560 - old performance issue, resolved as "Won't Fix".
1403 - assigned to Yash, but probably already fixed.
There are still sixteen old blocker or critical issues in open state that
have
not been addressed:
1874
1873
1870
1865
1863
1862
1855
1845
1797
1742
1725
1710
1549
1447
1402
1324
Future Business:
==================================================================================
1. Where to put release plans? CVS, Apache WIKI?
2. XPath public API to install built-in or non built-in functions.
3. 2093 - API for serializer to set line separator
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
