RE: [VOTE] Xalan-C 1.9 release

[Drazen DOTLIC]

Title: Message

+1, especially for VC7.1 project compatibility and ICU integration - we use both, and up to now we've been hacking the project files so that we can use them in VC7.1 ;)

-----Original Message-----
From: June Ng [mailto:[EMAIL PROTECTED]
Sent: 25. oktobar 2004 18:33
To: xalan-c-users@xml.apache.org
Cc: xalan-c-users@xml.apache.org; xalan-dev@xml.apache.org
Subject: Re: [VOTE] Xalan-C 1.9 release

+1

June K. Ng
XSLT Development
Email: [EMAIL PROTECTED]

Dmitry Hayes/Toronto/[EMAIL PROTECTED] 10/13/2004 03:58 PM Please respond to xalan-c-users

To xalan-dev@xml.apache.org, xalan-c-users@xml.apache.org cc Subject [VOTE] Xalan-C 1.9 release

Hi all!

Since the last release we have developed two significant enhancements for Xalan-C and we are thinking about releasing the new version .
The new , Xalan-C 1.9 release will include :

        -  Plagguble memory management : Xalan-C will be more stable in managing of the memory allocations and the user will be guarded against potential memory leaks
       -  Iterative processing : Xalan-C will be more stable in processing very big/deep XML files and stylesheets
       -  Xalan-C can be tested on the Unix platforms with "Conf"
       -  Compatibility with Xerces-C 2.6 and (optionally) ICU 3.0
       -  New compilers (addition of VC7.1  project files)
       -  Bug fixes

Our set of binary packages will be changed in accordance with the Xerces-C 2.6 release.
We will release on:
32 bit:
       - Win32 VC6 SP5
       - Linux RH8 / gcc 3.2
       - AIX 5.1 /xlC_r 6
       - HP 11i/ aCC 03.052
       - Solaris 2.8 Forte C++ 6.2
64 bit:
       - Linux SuSE 8.0 / gcc 3.2
       - AIX 5.1 /xlC_r 6
       - HP 11i/ aCC 03.052
       - Solaris 2.8 Forte C++ 6.2
       

I'd suggest to set Nov 12 as a target day , so the CVS code will be frozen from Nov 9 , Tuesday.

Any comments/suggestions are appreciated !

Please vote!

Here is my
+1



Thanks!
Dmitry Hayes

---

This message, including any attachments, is intended only for the person(s) to whom it is addressed. If you received it in error, please let us know and delete the message from your system. This message may be confidential and may fall under the duty of non-disclosure. Any use by others than the intended addressee is prohibited. Trema shall not be liable for any damage related to the electronic transmission of this message, such as failure or delay of its delivery, interception or manipulation by third parties, or transmission of viruses or other malicious code.