It seems to me like a good idea to put out a final release in the 2.x
series that is as stable as possible. 3.0 will be a significant change,
with a new build system, new features, and the removal of deprecated
APIs, which means that people may want to stick with 2.x for a while
because a) 3.x may be less stable for a while (or be assumed to be) or
b) they use features that are no longer present in 3.x. A final release
in the 2.x series that is really stable should keep the community happy
during the transition, which ought to lead to the peace and joy of a
(relatively) quiet mailing list. ;-)
To my mind, the ideal 2.7 release would fix all known bugs and introduce
no new (possibly buggy) features. That's probably not practical, but it
might be something to shoot for.
The final argument for 2.7: the last release in the 1.x series was 1.7.
Maybe there's something special about .7, or maybe there's a tradition
developing here, or maybe Xerces developers count in base 8 ("... 1.5,
1.6, 1.7 ... umm ... 2.0!").
> -----Original Message-----
> From: Neil Graham [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 02, 2005 11:32 PM
> To: [email protected]
> Subject: Xerces-C 2.7, to be or not to be?
>
> Hi folks,
>
> Although I'm pretty close to agnostic about this question, I
> thought it
> was worth asking whether anyone believes sufficiently strongly in the
> desirability of a Xerces-C 2.7 to make it happen? The
> argument for this
> would be that it would be nice to roll recent bugfixes and
> features into a
> release using the old but stable build system. The con would
> seem to be
> that although there have been plenty of bugfixes, the
> features added since
> 2.6 have generally been on the esoteric side.
>
> Thoughts? I notice that fixes are starting to be applied only to the
> trunk, so this is probably something we should arrive at a definitive
> position on fairly soon.
>
> Cheers,
> Neil
> Neil Graham
> Manager, XML Parser Development
> IBM Toronto Lab
> Phone: 905-413-3519, T/L 969-3519
> 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]
