You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by Neil Graham <ne...@ca.ibm.com> on 2004/02/04 02:56:26 UTC
[vote]: proposal for a Xerces-C 2.5.0 release
Hi folks,
As folks who've been following this list for a while will have noticed,
there's at least one particularly nasty bug in 2.4.0 that's driving folks
crazy. That is, the parser sometimes reports attributes as being
duplicates when namespaces are disabled even when that's most certainly not
the case.
But there are some other rather severe problems with 2.4.0 as well:
- The parser will often read freed memory while looking for duplicate
attributes;
- There are a considerable number of bugs in the XML Schema API
implementation. Most severe of these are a collection in the
getCanonicalRepresentation code that sometimes causes it to overwrite
random memory locations.
There have been myriad bugfixes applied recently as well, particularly to
improve thread safety, make sure the appropriate memory manager is used in
any context, and clean up compiler warnings.
So before we contemplate moving forward with development, perhaps it's a
good time to produce a bugfix release. Normally, one would like to
increment only the patch number and call this 2.4.1; but since so many
files have been touched since 2.4.0, it's unreasonable to assume we will
have binary compatibility on every platform. So that's why I'll propose to
call this 2.5.0.
I'll suggest that we should aim to publish this before the end of next
week, and in the mean time try and fix as many outstanding bugs (and commit
as many outstanding patches!) as possible. It would be wonderful if people
who have patches pending which have yet to be applied could retrofit their
patches to the current codebase, recognizing that it's unlikely any patches
made against the 2.4.0 source will apply cleanly now.
Here's my +1.
Cheers!
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [vote]: proposal for a Xerces-C 2.5.0 release
Posted by Vitaly Prapirny <ma...@mebius.net>.
Hi,
Neil Graham wrote:
> So before we contemplate moving forward with development, perhaps it's a
> good time to produce a bugfix release. Normally, one would like to
> increment only the patch number and call this 2.4.1; but since so many
> files have been touched since 2.4.0, it's unreasonable to assume we will
> have binary compatibility on every platform. So that's why I'll propose to
> call this 2.5.0.
I think it would be right.
Good luck,
Vitaly
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [vote]: proposal for a Xerces-C 2.5.0 release
Posted by Alberto Massari <am...@progress.com>.
+1 for me.
Alberto
At 20.56 03/02/2004 -0500, Neil Graham wrote:
>Hi folks,
>
>As folks who've been following this list for a while will have noticed,
>there's at least one particularly nasty bug in 2.4.0 that's driving folks
>crazy. That is, the parser sometimes reports attributes as being
>duplicates when namespaces are disabled even when that's most certainly not
>the case.
>
>But there are some other rather severe problems with 2.4.0 as well:
>
>- The parser will often read freed memory while looking for duplicate
>attributes;
>- There are a considerable number of bugs in the XML Schema API
>implementation. Most severe of these are a collection in the
>getCanonicalRepresentation code that sometimes causes it to overwrite
>random memory locations.
>
>There have been myriad bugfixes applied recently as well, particularly to
>improve thread safety, make sure the appropriate memory manager is used in
>any context, and clean up compiler warnings.
>
>So before we contemplate moving forward with development, perhaps it's a
>good time to produce a bugfix release. Normally, one would like to
>increment only the patch number and call this 2.4.1; but since so many
>files have been touched since 2.4.0, it's unreasonable to assume we will
>have binary compatibility on every platform. So that's why I'll propose to
>call this 2.5.0.
>
>I'll suggest that we should aim to publish this before the end of next
>week, and in the mean time try and fix as many outstanding bugs (and commit
>as many outstanding patches!) as possible. It would be wonderful if people
>who have patches pending which have yet to be applied could retrofit their
>patches to the current codebase, recognizing that it's unlikely any patches
>made against the 2.4.0 source will apply cleanly now.
>
>Here's my +1.
>
>Cheers!
>Neil
>Neil Graham
>XML Parser Development
>IBM Toronto Lab
>Phone: 905-413-3519, T/L 969-3519
>E-mail: neilg@ca.ibm.com
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [vote]: proposal for a Xerces-C 2.5.0 release
Posted by Berin Lautenbach <be...@wingsofhermes.org>.
Neil,
Sounds like a great idea!
As a very selfish question - if someone could incorporate bug 26426, I'd
be eternally gratefuly :>. (It's currently breaking the xml-security
library.)
Cheers,
Berin
Neil Graham wrote:
>
>
>
>
> Hi folks,
>
> As folks who've been following this list for a while will have noticed,
> there's at least one particularly nasty bug in 2.4.0 that's driving folks
> crazy. That is, the parser sometimes reports attributes as being
> duplicates when namespaces are disabled even when that's most certainly not
> the case.
>
> But there are some other rather severe problems with 2.4.0 as well:
>
> - The parser will often read freed memory while looking for duplicate
> attributes;
> - There are a considerable number of bugs in the XML Schema API
> implementation. Most severe of these are a collection in the
> getCanonicalRepresentation code that sometimes causes it to overwrite
> random memory locations.
>
> There have been myriad bugfixes applied recently as well, particularly to
> improve thread safety, make sure the appropriate memory manager is used in
> any context, and clean up compiler warnings.
>
> So before we contemplate moving forward with development, perhaps it's a
> good time to produce a bugfix release. Normally, one would like to
> increment only the patch number and call this 2.4.1; but since so many
> files have been touched since 2.4.0, it's unreasonable to assume we will
> have binary compatibility on every platform. So that's why I'll propose to
> call this 2.5.0.
>
> I'll suggest that we should aim to publish this before the end of next
> week, and in the mean time try and fix as many outstanding bugs (and commit
> as many outstanding patches!) as possible. It would be wonderful if people
> who have patches pending which have yet to be applied could retrofit their
> patches to the current codebase, recognizing that it's unlikely any patches
> made against the 2.4.0 source will apply cleanly now.
>
> Here's my +1.
>
> Cheers!
> Neil
> Neil Graham
> XML Parser Development
> IBM Toronto Lab
> Phone: 905-413-3519, T/L 969-3519
> E-mail: neilg@ca.ibm.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [vote]: proposal for a Xerces-C 2.5.0 release
Posted by James Berry <ja...@jberry.us>.
Here's my public +1... -jdb
On Feb 3, 2004, at 5:56 PM, Neil Graham wrote:
> Hi folks,
>
> As folks who've been following this list for a while will have noticed,
> there's at least one particularly nasty bug in 2.4.0 that's driving
> folks
> crazy. That is, the parser sometimes reports attributes as being
> duplicates when namespaces are disabled even when that's most
> certainly not
> the case.
>
> But there are some other rather severe problems with 2.4.0 as well:
>
> - The parser will often read freed memory while looking for duplicate
> attributes;
> - There are a considerable number of bugs in the XML Schema API
> implementation. Most severe of these are a collection in the
> getCanonicalRepresentation code that sometimes causes it to overwrite
> random memory locations.
>
> There have been myriad bugfixes applied recently as well, particularly
> to
> improve thread safety, make sure the appropriate memory manager is
> used in
> any context, and clean up compiler warnings.
>
> So before we contemplate moving forward with development, perhaps it's
> a
> good time to produce a bugfix release. Normally, one would like to
> increment only the patch number and call this 2.4.1; but since so many
> files have been touched since 2.4.0, it's unreasonable to assume we
> will
> have binary compatibility on every platform. So that's why I'll
> propose to
> call this 2.5.0.
>
> I'll suggest that we should aim to publish this before the end of next
> week, and in the mean time try and fix as many outstanding bugs (and
> commit
> as many outstanding patches!) as possible. It would be wonderful if
> people
> who have patches pending which have yet to be applied could retrofit
> their
> patches to the current codebase, recognizing that it's unlikely any
> patches
> made against the 2.4.0 source will apply cleanly now.
>
> Here's my +1.
>
> Cheers!
> Neil
> Neil Graham
> XML Parser Development
> IBM Toronto Lab
> Phone: 905-413-3519, T/L 969-3519
> E-mail: neilg@ca.ibm.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [vote]: proposal for a Xerces-C 2.5.0 release
Posted by Gareth Reakes <ga...@decisionsoft.com>.
+1
Gareth
On 6 Feb 2004, at 15:16, PeiYong Zhang wrote:
>
> +1
>
> PeiYong
>
> Neil Graham/Toronto/IBM@IBMCA wrote on 02/03/2004 08:56:26 PM:
>
> >
> >
> >
> >
> >
> > Hi folks,
> >
> > As folks who've been following this list for a while will have
> noticed,
> > there's at least one particularly nasty bug in 2.4.0 that's driving
> folks
> > crazy. That is, the parser sometimes reports attributes as being
> > duplicates when namespaces are disabled even when that's most
> certainly not
> > the case.
> >
> > But there are some other rather severe problems with 2.4.0 as well:
> >
> > - The parser will often read freed memory while looking for
> duplicate
> > attributes;
> > - There are a considerable number of bugs in the XML Schema API
> > implementation. Most severe of these are a collection in the
> > getCanonicalRepresentation code that sometimes causes it to
> overwrite
> > random memory locations.
> >
> > There have been myriad bugfixes applied recently as well,
> particularly to
> > improve thread safety, make sure the appropriate memory manager is
> used in
> > any context, and clean up compiler warnings.
> >
> > So before we contemplate moving forward with development, perhaps
> it's a
> > good time to produce a bugfix release. Normally, one would like to
> > increment only the patch number and call this 2.4.1; but since so
> many
> > files have been touched since 2.4.0, it's unreasonable to assume we
> will
> > have binary compatibility on every platform. So that's why I'll
> propose to
> > call this 2.5.0.
> >
> > I'll suggest that we should aim to publish this before the end of
> next
> > week, and in the mean time try and fix as many outstanding bugs
> (and commit
> > as many outstanding patches!) as possible. It would be wonderful
> if people
> > who have patches pending which have yet to be applied could
> retrofit their
> > patches to the current codebase, recognizing that it's unlikely any
> patches
> > made against the 2.4.0 source will apply cleanly now.
> >
> > Here's my +1.
> >
> > Cheers!
> > Neil
> > Neil Graham
> > XML Parser Development
> > IBM Toronto Lab
> > Phone: 905-413-3519, T/L 969-3519
> > E-mail: neilg@ca.ibm.com
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> > For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
> >
Re: [vote]: proposal for a Xerces-C 2.5.0 release
Posted by PeiYong Zhang <pe...@ca.ibm.com>.
+1
PeiYong
Neil Graham/Toronto/IBM@IBMCA wrote on 02/03/2004 08:56:26 PM:
>
>
>
>
>
> Hi folks,
>
> As folks who've been following this list for a while will have noticed,
> there's at least one particularly nasty bug in 2.4.0 that's driving
folks
> crazy. That is, the parser sometimes reports attributes as being
> duplicates when namespaces are disabled even when that's most certainly
not
> the case.
>
> But there are some other rather severe problems with 2.4.0 as well:
>
> - The parser will often read freed memory while looking for duplicate
> attributes;
> - There are a considerable number of bugs in the XML Schema API
> implementation. Most severe of these are a collection in the
> getCanonicalRepresentation code that sometimes causes it to overwrite
> random memory locations.
>
> There have been myriad bugfixes applied recently as well, particularly
to
> improve thread safety, make sure the appropriate memory manager is used
in
> any context, and clean up compiler warnings.
>
> So before we contemplate moving forward with development, perhaps it's a
> good time to produce a bugfix release. Normally, one would like to
> increment only the patch number and call this 2.4.1; but since so many
> files have been touched since 2.4.0, it's unreasonable to assume we will
> have binary compatibility on every platform. So that's why I'll propose
to
> call this 2.5.0.
>
> I'll suggest that we should aim to publish this before the end of next
> week, and in the mean time try and fix as many outstanding bugs (and
commit
> as many outstanding patches!) as possible. It would be wonderful if
people
> who have patches pending which have yet to be applied could retrofit
their
> patches to the current codebase, recognizing that it's unlikely any
patches
> made against the 2.4.0 source will apply cleanly now.
>
> Here's my +1.
>
> Cheers!
> Neil
> Neil Graham
> XML Parser Development
> IBM Toronto Lab
> Phone: 905-413-3519, T/L 969-3519
> E-mail: neilg@ca.ibm.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>
Re: [vote]: proposal for a Xerces-C 2.5.0 release
Posted by David Cargill <ca...@ca.ibm.com>.
+1 for me
David A. Cargill
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [vote]: proposal for a Xerces-C 2.5.0 release
Posted by Shiva Mamidisetty <sh...@abbnm.com>.
+1
Khaled Noaman wrote:
>
>
>+1
>
>
>
>
>
>
> Neil
> Graham/Toronto/IB
> M@IBMCA To
> xerces-c-dev@xml.apache.org
> 02/03/2004 08:56 cc
> PM
> Subject
> [vote]: proposal for a Xerces-C
> Please respond to 2.5.0 release
> xerces-c-dev
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>Hi folks,
>
>As folks who've been following this list for a while will have noticed,
>there's at least one particularly nasty bug in 2.4.0 that's driving folks
>crazy. That is, the parser sometimes reports attributes as being
>duplicates when namespaces are disabled even when that's most certainly not
>the case.
>
>But there are some other rather severe problems with 2.4.0 as well:
>
>- The parser will often read freed memory while looking for duplicate
>attributes;
>- There are a considerable number of bugs in the XML Schema API
>implementation. Most severe of these are a collection in the
>getCanonicalRepresentation code that sometimes causes it to overwrite
>random memory locations.
>
>There have been myriad bugfixes applied recently as well, particularly to
>improve thread safety, make sure the appropriate memory manager is used in
>any context, and clean up compiler warnings.
>
>So before we contemplate moving forward with development, perhaps it's a
>good time to produce a bugfix release. Normally, one would like to
>increment only the patch number and call this 2.4.1; but since so many
>files have been touched since 2.4.0, it's unreasonable to assume we will
>have binary compatibility on every platform. So that's why I'll propose to
>call this 2.5.0.
>
>I'll suggest that we should aim to publish this before the end of next
>week, and in the mean time try and fix as many outstanding bugs (and commit
>as many outstanding patches!) as possible. It would be wonderful if people
>who have patches pending which have yet to be applied could retrofit their
>patches to the current codebase, recognizing that it's unlikely any patches
>made against the 2.4.0 source will apply cleanly now.
>
>Here's my +1.
>
>Cheers!
>Neil
>Neil Graham
>XML Parser Development
>IBM Toronto Lab
>Phone: 905-413-3519, T/L 969-3519
>E-mail: neilg@ca.ibm.com
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [vote]: proposal for a Xerces-C 2.5.0 release
Posted by Khaled Noaman <kn...@ca.ibm.com>.
+1
Neil
Graham/Toronto/IB
M@IBMCA To
xerces-c-dev@xml.apache.org
02/03/2004 08:56 cc
PM
Subject
[vote]: proposal for a Xerces-C
Please respond to 2.5.0 release
xerces-c-dev
Hi folks,
As folks who've been following this list for a while will have noticed,
there's at least one particularly nasty bug in 2.4.0 that's driving folks
crazy. That is, the parser sometimes reports attributes as being
duplicates when namespaces are disabled even when that's most certainly not
the case.
But there are some other rather severe problems with 2.4.0 as well:
- The parser will often read freed memory while looking for duplicate
attributes;
- There are a considerable number of bugs in the XML Schema API
implementation. Most severe of these are a collection in the
getCanonicalRepresentation code that sometimes causes it to overwrite
random memory locations.
There have been myriad bugfixes applied recently as well, particularly to
improve thread safety, make sure the appropriate memory manager is used in
any context, and clean up compiler warnings.
So before we contemplate moving forward with development, perhaps it's a
good time to produce a bugfix release. Normally, one would like to
increment only the patch number and call this 2.4.1; but since so many
files have been touched since 2.4.0, it's unreasonable to assume we will
have binary compatibility on every platform. So that's why I'll propose to
call this 2.5.0.
I'll suggest that we should aim to publish this before the end of next
week, and in the mean time try and fix as many outstanding bugs (and commit
as many outstanding patches!) as possible. It would be wonderful if people
who have patches pending which have yet to be applied could retrofit their
patches to the current codebase, recognizing that it's unlikely any patches
made against the 2.4.0 source will apply cleanly now.
Here's my +1.
Cheers!
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org