Xalan-J JIRA defect review - Tuesday February 7, 2006 from 2:00 to 3:30 pm EST - Minutes

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

======================================================================================


 SUBJECT:  Xalan-J JIRA defect review - minutes review
 WHEN:     Tuesday February 7, 2006 from 2:00 to 3:30 pm EST
 INVITEES: Active Apache Xalan contributors
 CHAIR:    Brian Minchau
 WHERE:    Teleconference
 Phone for Toronto Area: (***) ***-****
 Phone for Others: (***) ***-****
 Conference ID for all: *****

 LAST MEETING WAS ON: Tuesday July  12, 2005

Outline:
 0. Roll call
 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


 ====================================
 ====================================
 0. Roll call
Present:
 - Henry Zongaro
 - Ilene Seeleman
 - Christine Li
 - Brian Minchau
 ====================================
 ====================================
 1. Old Business

 a) In the last meeting this issues
 were covered: 2169 back through 2137
 b) In previous meetings issues
 covered: 2136 back through 2032

 ====================================
 ==================================
 2. Brief Summary of defect arrival
 and resolution



 March 2005 2068-2090 : 23 new  issues
 April 2005 2091-2111 : 21 new  issues
 May 2005 2112-2132 : 21 new  issues
 June 2005 2133-2164 : 32 new issues
 July 2005 2165-2176 : 12 new issues
 August 2005 2177-2192 : 16 new  issues
 September 2005 2193-2206 : 14 new  issues
 October 2005 2207-2222 : 16 new  issues
 November 2005 2223-2240 : 18 new  issues
 December 2005 2241-2250 : 10 new  issues
 January 2006 2251-2264 : 13 new  issues
 February 2006 2265-2265 : 2 new  issues ... so far

 Currently unresolved and opened in  the given month:
 2005, March     2071, 2072, 2078, 2088  : 4 of 23 unresolved
 2005, April     2091, 2092, 2094, 2100, 2106, 2107, 2108, 2111 : 8 of 21
unresolved
 2005, May       2112, 2113, 2118, 2119, 2127, 2130  : 6 of 21 unresolved
 2005, June      2133, 2137, 2150, 2151, 2152, 2153, 2155, 2157, 2160 : 9
of 32 unresolved
 2005, July      2165, 2166, 2168, 2169, 2171, 2173 : 6 of 12 unresolved
 2005, August    2177, 2178, 2180, 2186, 2187, 2188, 2189, 2190, 2191, 2192
: 10 of 16 unresolved
 2005, September 2193, 2194, 2195, 2196, 2197, 2198, 2200, 2201, 2202,
2203, 2204, 2205, 2206  : 13 of 14 unresolved
 2005, October   2208, 2209, 2210, 2211, 2212, 2215, 2216, 2118, 2119,
2221, 2222 : 11 of 16 unresolved
 2005, November  2223, 2224, 2225, 2227, 2229, 2233, 2234, 2236, 2238,
2239, 2240 : 11 of 18 unresolved
 2005, December  2241, 2242, 2243, 2244, 2246, 2248, 2250, 2252 : 8 of 10
unresolved
 2006, January   2253, 2254, 2255, 2256, 2257, 2258, 2259, 2260, 2261,
2262, 2263, 2264 : 12 of 13 unresolved
 2006, February  2265, 2266 : 2 of 2 unresolved


 Previous Open or re-opened issue
 backlog:
 April 5, 2005: 411
 May 3, 2005: 409
 June 6, 2005: 421
 July 12, 2005: 416
 February 7, 2006: 446

> For the latter half of 2005 we were holding steady around 410 defects,
but
  in the last months the open count has jumped up to 446.



 ====================================
 ==================================
 3. New Issues Opened Since Last
 Meeting, plus assigned issue status


 3.a) Open issues with a patch

> this meeting focused on issues that have a patch already,
   to work on low hanging fruit.


 XALANJ-2264 on xi:include
 > Patch needs to be more robust to be taken into Xalan-J
 > Other parer options need to be considered, such as validating
 > This is the Process command. If someone really needs these APIs
   they can use JAXP APIs. Do we need to support every possibility
   through the Process command?
 > Entity resolver is the only real parser option that we handle
   with "Process"
 > This impacts the products APIs and documentation, so we are
   hesitant to do this.
 > Brian M. will look at existing parser options.

XALANJ-2253 "synchronized"
 > Large patch
 > Think this code has been looked at before that this synchronized
   block was needed and as small as it could be.

XALANJ-2243
> Looks like the user wants the value of an attribute to have
  disable output escaping applied to it, but this only
  applies to text nodes.
> Henry Z. will respond to issue.

XALANJ-2242
> no change.

XALANJ-2240
> Patch looks right.
> Brian M. will apply patch.

XALANJ-2239
> no change.

XALANJ-2236
> no change.

XALANJ-2224 "new collecation APIs"
> The suggested APIs are as of JRE 1.2, so it is OK to change to them.
> The purpose of the patch is to make experientation easier, to use another
  implementation of List.
> Brian M. to look at patch.

XALANJ-2222
> Brian M. to deal with this one.

XALANJ-2221
> Aready assigned to John G.

XALANJ-2218
> Looks to be correct, the default setting is wrong.
> m_escapeSettings flag. Current default value is "yes" or false but should
be "no"
> Only an issue for SAX.
> Brian M. to take this one.

XALANJ-2208
> Already assigned to John G. as reviewer

XALANJ-2205
> Brian needs to apply the patch

XALANJ-2196
> Henry has looked at build issues before and will review.

XALANJ-2157
> Was discussed in another JIRA meeting,
  and the problem with this patch is that it
  makes the interpretive processor depend on
  XSLTC.  Not using the usual mechanisms for
  finding service providers. It uses a system
  property to find the name of a service.

> It a reasonable feature but should use
  the usual mechanism for getting a service
  provider.
> Henry Z. agreed to post comments.

XALANJ-2137
> no change.

XALANJ-2133
> Morris already reviewed path
> Brian needs to commit.

XALANJ-2130
> no change.

XALANJ-2127
> In Santiaogo P-G's hands already
> The patch to XSLTC was based on
  2.6 code, and CallFunction class was
  deleted recently   by Christine Li
  as part of a security fix at the
  end of 2005.
> This works for interpretive in 2.7
  but fails for XSLTC.
> The patch is no longer appropriate
  but the functionality is still
  missing.



 ====================================
 ==================================
 4. Round table discussion

 a) New option in feature 2264, "
 Supporting xi:include on xalan
 command-line ", does it need a new
 release?
 > No, not a new release, we've added
   options without a new release before,
   so a point release is sufficent.