Bravo!  Now that you mention the idea, it seems obvious, and I
appreciate your willingness to step up to the plate and make it happen.

One thing I'm unsure of, though, is who would build all the pre-compiled
libraries.  Are you (Boris) in a position to build them all (25, by my
count), or do you know who can?  (Sadly, all I can build is 32-bit MSVC,
which I imagine is already covered.)

-----Original Message-----
From: Boris Kolpackov [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, August 14, 2007 3:04 AM
To: [email protected]
Subject: Xerces-C++ 2.8.0 release plan

Hi,

[My original message didn't get through so this is a re-post.]

It's been almost two years since the release of Xerces-C++ 2.7.0.
While there are preparations to release 3.0 soon, many existing
applications won't be able to use 3.0 immediately because of the
extensive API changes but would greatly benefit from a large number
of bug fixes that have been committed to the xerces-2.7 branch. For
example, the tool I am working on does not compile with the 3.0
code and if I change the code to use 3.0 interfaces it will stop
compiling with 2.7. I also regularly receive bug reports against
Xerces-C++ on our mailing list only to find out that they were fixed
years ago. I have to routinely extract and send patches for issues
like 1281, 1546 (schema bugs that affect several widely-used schemas,
such as GML, COLLADA, etc.) and 1658 (a binary stream bug that makes
Xerces-C++ 2.7.0 virtually unusable on Solaris).

I therefore would like to volunteer as a release manager for 2.8.0.
Once 2.8.0 is released, I am prepared to act as a release manager
and push for 3.0.

The xerces-2.7 branch appears to be stable. I also have the following
improvements ready:

* Support for g++ on AIX and HP-UX.

* Auto-detection of aCC6 vs aCC3 in runConfigure.

* Verbose mode (gmake VERBOSE=1)

* Changed optimization level for GNU/Linux from -O to -O2

* Project files for VS 2005.

* Support for 64 bit Windows build.

* Optimized DOM parsing (25-30% improvement), see XERCESC-1735
  for details: https://issues.apache.org/jira/browse/XERCESC-1735

Xerces-C++ is normally released with pre-compiled libraries for
various platforms. For the 2.8.0 release the proposed list of
platforms/compilers is as follows:

32 bit:

   Windows - MSVC 7.1
   Windows - MSVC 8.0
   GNU/Linux - g++ 3.4.x
   AIX 5.3 - xlC 7
   Solaris 2.10 - Sun C++ 5.7 and g++ 3.4.x, both SPARC and x86
   HP-UX 11.x - aCC A.03.x, PA-RISC
   HP-UX 11.x - aCC A.06.x, IA64
   Mac OS X 10.4 (Tiger) - g++ 4.0, both PPC and x86

64 bit:

   Windows - MSVC 8.0
   GNU/Linux - g++ 3.4.x
   AIX 5.3 - xlC 7
   Solaris 2.10 - Sun C++ 5.7 and g++ 3.4.x, both SPARC and x86-64
   HP-UX 11.x - aCC A.03.x, PA-RISC
   HP-UX 11.x - aCC A.06.x, IA64

I propose we take the following next steps in order to release
2.8.0 in a timely manner:

1. Announce this plan on the c-users mailing list and ask for any
   critical issues that the community feels need to be addressed.

2. Package and announce a release candidate. Test it on the above
   platforms. Fix any uncovered issues.


Any feedback on this plan and/or the platforms list is appreciated.


Thanks,
Boris


-- 
Boris Kolpackov
Code Synthesis Tools CC
http://www.codesynthesis.com
Open-Source, Cross-Platform C++ XML Data Binding

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


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

Reply via email to