At 16.13 02/12/2005 -0800, James Berry wrote:
Hi Jason,
The most up-to-date code for 3.0 is on the main trunk.
I apologize to all for being distracted on this project. I'd like to
gauge interested by committers in getting 3.0 out the door, and
solicit comments on how close we are...I'd be happy to help as I can
with remaining issues, but I believe them to be mostly platforms
specific and so they'll require particular help on the particular
platforms.
Comments?
This is the situation for the tasks where I was involved:
- DOM 3.0 support: interfaces have been updated; Axel is working on
implementing the DOMTypeInfo::isDerivedFrom API. Documentation still
has to be updated, and a migration guide is missing altogether
- Platforms support: I have tested the Windows compilers Borland
5.51, Visual C++ 6.0, 7.1 and 8.0 (no 7.0 - I don't have it), MinGW
and gcc on RedHat; Interix has issues with the autoconf scripts, and
MinGW crashes trying to produce DLLs.
- the ACE-based NetAccessor is written, but BoundsChecker thinks it
leaks memory, so I still have to work on it
So, we are missing the reports on whether the new build
infrastructure works on other Unix platforms (AIX, HPUX, 64-bit
hardware, OS390, Solaris, Cygwin); some brand new features like
XInclude and RelaxNG didn't started; and if we want to reorganize the
source tree, some schema-related files could be moved from
framework\psvi into validators\schema.
In any case, given that 2.7 released in September, I wasn't
forecasting a 3.0 release at least until March 2006.
What do the other committers think?
Alberto
James
On Dec 2, 2005, at 8:24 AM, Jason E. Stewart wrote:
Hey All,
I've been asked to release a snapshot of Xerces-P for Xerces-C-3.0.
I appologize, but I haven't been monitoring the list for some
time. What is the status of the 3.0 release? Is the most up-to-date
code in the jberry/3.0 branch? Or is there another?
Cheers,
jas.
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
