Hi all,

I've been pretty quiet lately, but here's a +1 anyway.

I think the concerns James and Scott have articulated are very valid, and 
in the last couple of days quite a number of critical bugs have been 
killed off.  All I'd point out is that we have in Xerces-C 2.5 a precedent 
for pushing out a new release if a previous one has significant problems. 
Personally, I'd be totally fine with pushing out a new Xerces release if 
people kick the tires of 2.6 and find some really bad flaws--or if a 
critical mass of really bad bugs get fixed in the next month or so. 

That said, having some formal guidance in place about what Jira needs to 
look like in order for a release to be posted does seem only prudent. 

Cheers,
Neil
Neil Graham
Manager, XML Parser Development
IBM Toronto Lab
Phone:  905-413-3519, T/L 969-3519
E-mail:  [EMAIL PROTECTED]





PeiYong Zhang/Toronto/[EMAIL PROTECTED] 
Sent by: PeiYong PY Zhang/Toronto/[EMAIL PROTECTED]
09/23/2004 03:26 PM
Please respond to
xerces-c-dev


To
[EMAIL PROTECTED]
cc

Subject
[VOTE]:  Proposal for a Xerces-C2.6.0 release







Hi all, 

   There are many bug fixes[1] to the XercesC2_5_0 and new features[2] 
implemented since 
the release of XercesC2_5_0, it is time to produce a new release, 
XercesC2_6_0. 
    
   I'll suggest that we should aim to publish this by the end of 
September, and in the mean 
time try and fix as many outstanding bugs as possible before the closing 
time, EST 12:00 PM, Sept. 29. 

Here's my +1. 

Rgds, 
PeiYong 

XML Parsers Development, IBM Toronto Laboratory
D2-265, 8200 Warden Ave, Markham, Ont L6G 1C7, Canada

Email: [EMAIL PROTECTED]
Phone: (905)413-4088 Fax: (905)413-4854; T/L: 778-4088 

[1] Fixes: 
. ComplexTypeInfo thread safety 
. Crash of complex types with MixedContentModel 
. IG/SGXMLScanner: fErrorStack cleared if an exception is thrown 
. SchemaValidator: reset() clear stack of types 
. ComplexTypeInfo: Thread-Safety Issue 
. XSerializeEngine: Supplied Memory Manager used 
. RangeTokenMap::instance(): Thread-Safety Issue 
. Grammar Caching: Parsing instance document with DTD 
. Fix to a problem in which, when grammar caching is enabled and dynamic 
validation is 
  also enabled, the parser would fail to correctly process a document with 
no grammar 
  following correct processing of a schema-valid document with no 
namespace. 
. Memory Leakage: Parsing instance document with DTD 
. A number of performance improvements, particularly for non-validating 
parsing 
. Grammar pools are now passed complete grammar descriptions, rather than 
grammar descriptions 
  only containing schemaLocation hints 
. 390 threading 
. Make parser work where new transcoding instructions not present 
. 390 file resolution problem 
. 390 intrinsic transcoding support 
. Grammar serialization bug fixes 
. Other minor bug fixes (PSVI, potential memory leaks in constructors) 

[2] Features 
. Reduce footprint of DLL by building the deprecated DOM as a separate 
library 
. Enable ID's to work on all kinds of schema components 
. Add messages to DOMExceptions along with the error code. 
. Improve annotation error-reporting capabilities 
. Make grammar caching work with DTD internal subsets.   
. Bring parser up to the XML 1.0 3rd Edition. 
. Update to the XML 1.1 recommendation   
. Update Schema Errata 
. Add new method to DOMDocument so that DOM level-2 style DOMDocumentTypes 

 (which have a DOMDocument to own them) can be created.   
. Feature for disabling identity constraints 
. Support HP on Itanium 
. Provide means to get actual values out of PSVI/schema component model. 
. Synthesize annotation components for non-schema attributes 
. Expose partial PSVIElement information at the start element call 
. Upgrade to ICU3 .0 
. Externalize validation, actual/canonical value production for arbitrary 
strings 
. Laxly validate schema annotations 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to