Xalan-J bug triage agenda for Tuesday July 12, 2005 (2 pm EDT) 2005-07-11 - By Brian Minchau
NOTE: For those of you worried about Apache protocol, no decisions are
made at this meeting. No voting on issues is done either.
Any committer is free to assign a bug to themself, to fix a bug
etc. All that this meeting does is to facilitate communication
between active Xalan-J committers on technical issues.
As always, all active Xalan-J committers are welcome on this call,
just e-mail me for the teleconference information. - Brian Minchau
SUBJECT: Xalan-J JIRA defect review
WHEN: Tuesday July 12, 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 June 7, 2005
Agenda Outline:
1. Old Business
2. Brief Summary of defect arrival and resolution
3. New Issues Opened Since Last Meeting, plus assigned issue status
4. Round table discussion
5. Older open blocker or critical issues
6. Older open non-blocker non-critical issues
AGENDA
======================================================================
1. Old Business
a) In the last meeting this issues were covered: 2140 back through 2112
b) In previous meetings issues covered: 2113 back through 2032
======================================================================
2. Brief Summary of defect arrival and resolution
Since the last meeting 20 issues resolved in June
(compared to 21 in May, 22 in April, and 27 in March):
2167, 2164, 2162, 2161, 2159, 2158, 2156, 2146, 2140, 2124
2097, 2076, 2002, 1978, 1870, 1863, 1840, 1640, 1403, 1171
Since the last meeting, 24 new issues
(compared to 29 in May, 19 in April, 20 in March) :
2163 back through 2141.
We now have a total of 416 issues not resolved or closed
(compared to 421 on June 6, 409 on May 3, 411 on April 5, 2005).
======================================================================
3. New Issues Opened Since Last Meeting, plus assigned issue status
3.a) New issues needing assignment:
???? - since the agenda came out
2169 -
2168 -
2165 -
2163 -
2160 -
2157 -
2155 -
2154 -
2153 -
2152 -
2151 -
2150 -
2149 -
2148 -
2147 -
2145 -
2144 -
2143 -
2142 -
2137 -
3.b) Open assigned issues with no patch (just a reminder):
Brian M. : 2087, 2050, 1974, 1855, 1698, 1536
Christine L. : 2055, 1447
Henry Z. : 2057, 2001, 1973, 1851, 1845
Joanne T. : 2120, 2107, 2100, 2094
John G. : 2114, 2113, 1574
Morris K. : 1263, 1139, 1086, 1065, 739
Ramesh M. : 2106, 2063, 2062
Santiago P-G : 2040, 2032, 1912, 1485, 1151
Sarah M. : 2144, 2129, 2065
Yash T. : 2150, 2149, 2148, 2083, 2072, 2056, 2043, 2042, 2041, 2039,
1923
3.c) Open issues with a patch, needing a reviewer:
2157
2147
2099
2078
2061 - Cleanup some dead code
3.d) Open issues with a patch, needing a review by the reviewer (just a
reminder):
Brian M. : 2023
Christine L. : 1867
Henry Z. : 2137, 2130
3.e) Open issues with a patch and review approval, needing a commit to CVS
Brian M. : 2133, 2103
======================================================================
4. Round table discussion
a) Target date for Xalan-J 2.7 release is August 4, 2005,
code freeze July 28, 2005.
b) bugs that we might want to get fixed in 2.7 release.
- 2083 (fp1) Data corrupted in Parallel XSL execution
- 2043 (fp1) Concurrency problem with template parameters
- 2042 (fp1) Concurrency probmem with recursive template
- 2041 (fp1) Concurrency problem with HTML Serialization
- 2024 (fp1) Axis name: preceding-sibling:: does not seem to work
- 2150 (fp2) Namespace Undeclaration in XML input document is not
handled correctly.
- 2149 (fp2) Namespace Undeclaration in XML input document is not
handled correctly.
- 2124 (fp2) committed, done, but needs a reviewer
- 2100 (fp2) Unrecognized Namespace beginning with '//'
- 2088 - Passing initial mode from command line
(accepted as a request, not assigned)
- 2087 - Get rid of dependency on sun.io.CharToByteConverter (John G.
to review)
need to apply this patch for 2.7.0 as it fixes numerous issues
with various encodings.
- 2032 (fp2) XSLTC: Multiple namespace prefixes produce unexpected
prefixes in output
c) features for 2.7 release
- JAXP 1.3 (Morris K. has committed the work, Ilene S. has agreed to
review)
- XML 1.1 ( Yash had one bug that he was going to fix, was it fixed?)
- Serializer xsl:output property to set end of line sequence, done
through 2093.
- JNDI contribution through John G. ?
d) Other?
======================================================================
5. Older open blocker or critical issues
1845 - Transformation leads to random SAXParseException (data not bounded
properly) when stressed
1742 - Order of global variable and param affect the output
1725 - Xalan 2.5.2 XSLTC: <xsl:copy-of> loses both ATTRIBUTES & NAMESPACES
1549 - XSLT Error (javax.xml.transform.TransformerConfigurationException):
Could not load the translet class
1402 - Incorrect usage of context ClassLoader for static field
initialization
(The suggested fix was put in XALANJ-1411, the code was applied,
issue resolve - suggest closing this issue)
1324 - XSLTC compiltation error : Branch target offset too large for short
======================================================================
6. Older open non-blocker, non-critical issues (assuming we make it this
far in the agenda)
2083 - Data corrupted in Parallel XSL execution
(Got a testcase since last JIRA meeting, not yet assigned)
2071 - DOM2SAX reports Null-Namespace via 'null' value, should be empty
String ""
(Santiago or Ramesh did not accept assignment, still unassigned)
2067 - Multiple executions of transformation having DOM Document as
parameter is not working
(looks like a legitimate bug, no volunteer to assign to)
2031 - Grouping filter with preceding/following axis produces wrong nodeset
2029 - XML file must contain LF, CRLF or CR are unsupported
2028 - Doc about redirect should be clear about AVTs
2022 - XMLErrorResources and XPATHErrorResources mix messages with Java
code
2020 - XMLErrorResources - some messages not translated
2016 - Text outside elements that can't be represented in specified
encoding is not escaped
2014 - ExsltDatetime functions do not support fractional seconds values
2010 - getMessageAndLocation() api of TransformerException return stack
trace along with the error message 2002 - backward compatibility with
exsl
2001 - normalize-space gives StackOverflowError
2000 - xsl:include with relative href cause MalformedURL on unicode path
1996 - Error needed for xsl:apply-imports evaluated while evaluating
top-level variable
1995 - CachedXPathAPI doesn't cache under some cases
....
|
|
