At 16.16 11/06/2007 -0400, Michael Glavassevich wrote:
Hi Boris,
I'm not sure. I'm mostly just a causal observer here. If anyone has a good
handle on what's left to do, it's probably Alberto and Dave since they're
most active here these days.
Yes, the only remaining issue is having Xerces
Hi,
I would like to fix the build on AIX. Plz tell me how to get the
latest source.
Regards
Raman
From: Alberto Massari [EMAIL PROTECTED]
Reply-To: c-dev@xerces.apache.org
To: c-dev@xerces.apache.org
Subject: Re: Is a 3.0 release in the foreseeable future?
Date: Tue, 12 Jun 2007
At 20.22 12/06/2007 +0530, Ramanjaneyulu malisetti wrote:
Hi,
I would like to fix the build on AIX. Plz tell me how to
get the latest source.
Regards
Raman
From: Alberto Massari [EMAIL PROTECTED]
Reply-To: c-dev@xerces.apache.org
To: c-dev@xerces.apache.org
Subject: Re: Is a 3.0 release
Hi Alberto,
Thanks for the information!
Alberto Massari [EMAIL PROTECTED] writes:
Yes, the only remaining issue is having Xerces build on the platforms
for which binaries are usually built (Windows - RedHat - AIX -
Solaris - HPUX for 32 bit, SuSE - AIX - Solaris - HPUX for 64 bit).
As the
Hi Boris,
At 19.49 12/06/2007 +, Boris Kolpackov wrote:
Hi Alberto,
Thanks for the information!
Alberto Massari [EMAIL PROTECTED] writes:
Yes, the only remaining issue is having Xerces build on the platforms
for which binaries are usually built (Windows - RedHat - AIX -
Solaris - HPUX
Hi Michael,
Thanks for the link. The information for most of the entries on that page
seems to be rather outdated (7 months old). Do you know if successful build
on these platforms is the only remaining issues that prevents the release?
I also wonder if there is a release manager of some sort for
Hi Boris,
I'm not sure. I'm mostly just a causal observer here. If anyone has a good
handle on what's left to do, it's probably Alberto and Dave since they're
most active here these days.
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: [EMAIL PROTECTED]
E-mail:
See subject...
I really could use the application heap sizing before I ship, or I'll
have to keep issuing my own Xerces packages, I can't live with a 64K
allocation per document.
I don't have a lot of time to test exhaustively, but I'll certainly be
able to exercise the build and test what
Hi,
I would also like to know what is the current status and if there
is anything I can do to help the process.
Thanks,
Boris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
I believe one of the things that has been holding back this release are
the build failures which have been occurring on some of the platforms. The
status for these is being tracked on the Wiki here [1]. I'm sure the
Xerces-C developers would appreciate help from the community to fix these
7:54 PM
Subject: Re: 3.0 release candidate nearing completion
To: p-dev@xerces.apache.org
On Sat, 9 Sep 2006, Jason Stewart wrote:
Hey All,
There hasn't been much activity on the list for a while, so I thought
I would create a little excitement.
Xerces-P has officially merged with Xerces-C
Hey,
On 3/31/06, Gareth Reakes [EMAIL PROTECTED] wrote:
Hey,
Jason, do you have any thoughts on generating .net/python etc
interfaces from what you have. Is it as simple as pressing go?
In the future, yes. At them moment I would need help from someone who
knows .net and python to
Jason Stewart [EMAIL PROTECTED] writes:
Which means that we need to set a date for C++ code freeze ;-)
Or, at least, a freeze on modifications to public interfaces. This
will also benefit my effort to squash warnings on various platforms.
-boris
Hey,
I have a couple of changes to make, but could make them without
actually implementing them. What about other people? What kind of time
line are we looking at?
Jason, do you have any thoughts on generating .net/python etc
interfaces from what you have. Is it as simple as pressing go?
At 09:18 AM 3/31/2006 +0100, Gareth Reakes wrote:
Hey,
I have a couple of changes to make, but could make them
without actually implementing them. What about other people? What
kind of time line are we looking at?
I'll try to make the LSInput/LSOutput-related changes between today
Hey,
On 3/22/06, Gareth Reakes [EMAIL PROTECTED] wrote:
I think the Xerces-P integration is completed;
Jason, you good to go?
I'm good to go - but I need time to update everything after the C++
code freeze has started. I have to recompile all my interfaces with
the latest C++ headers.
One
Gareth,
Gareth Reakes [EMAIL PROTECTED] writes:
what about compilation on
the other Unix platforms (Solaris, OS/390, TRUE-64...)?
Can we have some volunteers for platform testing please? We don't have
access to all the platforms so help would be great. We can support you
in doing this if
On Mar 23, 2006, at 10:26 AM, Boris Kolpackov wrote:
Gareth,
Gareth Reakes [EMAIL PROTECTED] writes:
what about compilation on
the other Unix platforms (Solaris, OS/390, TRUE-64...)?
Can we have some volunteers for platform testing please? We don't
have
access to all the platforms so
Gareth Reakes wrote:
Axel doesn't have the time to implement the
DOMTypeInfo::isDerivedFrom API).
Axel, are we putting this off until next release? No problem if so,
but if you need just a bot more time we can do release around that
date.
Hi all,
I have been trying to take my time to
Hey,
Hi Gareth,
the status didn't change much on my side (well, it got worse because
Axel doesn't have the time to implement the DOMTypeInfo::isDerivedFrom
API).
Axel, are we putting this off until next release? No problem if so, but
if you need just a bot more time we can do release
20 matches
Mail list logo
