SUBJECT: Xalan-J JIRA defect review minutes
WHEN: Tuesday June 7, 2005 from 2:00 to 3:30 pm EDT
INVITEES: Active Apache Xalan committers
CHAIR: Brian Minchau
WHERE: Teleconference
Phone for Toronto Area: (???) ???-????
Phone for Others: (???) ???-????
Conference ID for all: ???????
LAST MEETING WAS ON: Tuesday May 3, 2005
======================================================================
0. Attendees
Brian Minchau
Christine Li
Henry Zongaro
Joanne Tong
John Gentilin
Morris Kwan
Sarah McNamara
Yash Talwar
======================================================================
1. Old Business
a) In the last meeting this issues were covered: 2113 back through 2093
b) In previous meetings issues covered: 2092 back through 2032
======================================================================
2. Brief Summary of defect arrival and resolution
Since the last meeting 21 issues resolved
(compared to 22 in April, and 27 in March):
2139, 2134, 2126, 2125, 2123, 2122, 2121, 2117, 2116, 2109,
2101, 2093, 2069, 1895, 1876, 1844, 1778, 1701, 1660, 1572
296
Since the last meeting, 29 new issues
compared to 19 in April, 20 in March) :
2140 back through 2112. It should be noted that six
of these are due to Morris working on JAXP 1.3 support,
so the user related defect arrival rate is holding steady.
We now have a total of 421 issues not resolved or closed
(compared to 409 on May 3, 411 on April 5, 2005).
======================================================================
3. New Issues Opened Since Last Meeting, plus assigned issue status
New issues needing assignment:
2140 - Henry Z. volunteered to fix (already has patch),
Brian M. to review, to go in 2.7 release
2138 - Doesn't look like a legitimate problem.
Henry Z. will update the issue
2136 - Assign to Morris K.
2135 - Assign to Morris K.
2132 - Assign to Brian M.
2131 - Henry provided a response, but not assigning to anyone yet.
2129 - Assign to Sarah McNamara, put in the list to fix for 2.7.0
2128 - Henry resolved this one as already fixed,
but only in current CVS (thanks Henry)
2127 - Set to fp3.
2120 - Assign to Joanne T., she will get clarification from W3C on
empty HTML elements that have non-empty content (like <BR>)
Brian M. will look at
the problem that a <BR> element is totally lost,
which is a second bug reported in the issue.
2119 - Set to fp4.
2118 - Set to fp3, assign to Brian M.
2115 - Resolved as duplicate by Henry Z.
2114 - Assign to John G., reviewer Brian M., to fix for 2.7.0
2113 - Assign to John G.
2112 - Class Cast Exception in NodeSortRecord
All JAXP 1.3 issues will be assigned to Morris K.,
Brian will ask Ilene S. to review Morris' patches.
Open issues with a patch, needing a reviewer:
2103 - Case of doctype definition wrong
2087 - John G. agreed to review patch, to get in 2.7.0 release.
2078 - Yash T. agreed to look at this one and come up
with a true patch file.
======================================================================
4. Round table discussion
a) Tentative date for Xalan-J 2.7 release is mid July 15 with
code freeze or code slush set for July 8 to 15.
b) bugs that we might want to get fixed in 2.7 release
that are of fix priority fp1, or fp2.
- 2102 (fp1) - works in current CVS, note sent to Ramesh to
see if there is any progress on this as a
JDK 1.4.2_05 problem.
- 2083 (fp1) - Yash couldn't reproduce yet, not targeted for 2.7
- 2043 (fp1) - Yash will revisit if this will make 2.7
- 2042 (fp1) - Yash will revisit if this will make 2.7
- 2041 (fp1) - Yash will revisit if this will make 2.7
- 2024 (fp1) - Brian will try to reproduce this one.
If Yash can reproduce the multi-threaded problems we may need to
look into redistributing them.
- 2124 (fp2) - Assigned to Morris K. for 2.7
- 2100 (fp2) - Joanne to look at this one
- 2097 (fp2) - Henry to look at this one
- 2032 (fp2) - Note sent to Santiago, to see if there is
progress on this one.
- 1938 (fp2) - New reworked patch by Henry, for 2.7
c) features for 2.7 release
- JAXP 1.3 - Morris has opened all necessary JIRA issues, just need
to complete the patches, and reviews and commits to the code base.
- XML 1.1 - Yash is aware of a bug and will
open a JIRA issue to track it.
- Serializer xsl:output property to set end of line sequence - done
- JNDI support for SQL extensions. John G. is waiting for a
latest code iteration from Eric (who has signed a CLA).
John will get the code any day and will be the reviewer
and committer. The SQL extension are difficult to
test because a database is needed, and there are
licensing issues. John will run unit tests, and will write a
small document on how to setup and run, and
put in the examples directory. John will create a DB2 flavour
of the JNDI example. There is also documentation on the
samples page that could be updated.
d) When 2130, 2133, 2137 are applied to the code base XSLTC
will support all of the Xalan-J interpretive extensions to
the <xsl:output> element (previously
there was only support for indent-amount). The one exception
is that the content-handler attribute will not be supported
by XSLTC.
These properties can be set in the stylesheet or via JAXP,
however due to the nature of the test harness it is easier
to set the extension attributes in
a stylesheet can add it to the "accept" bucket.
Brian will revisit test coverage of extension attributes set
in the stylesheet, including the new line-separator,
for both Xalan-J interpretive and XSLTC.
Joanne T. will work with Brian on this.
e) John G. is working on is to expose the Java Mail APIs as Xalan
extensions and functions so you can send an e-mail with
attachments or read an e-mail from an account all as part
of a transformation. Is Xalan interested in this code,
it could be contributed to Apache.
However this would put a build dependancy on the Java Mail APIs.
Could this be a feature of Xalan just like SQL support is,
or could it be a sub-project.
Do we need to have this go through the Apache incubator?
The Java Mail API is not open source, and we would probably
need a jar checked in to ./java/bin. However there may be
license issues as the Java Mail API is under the
"Java Research License" and can probably not use things derived
from it for commercial purposes. It is not clear if that restriction
is for source code, or for the binaries as well. This license
issue is independent of whether it is a feature of Xalan,
or a sub-project, and needs to be raised with the PMC.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
