Hey Boris,

On Aug 20, 2007, at 3:27 PM, Boris Kolpackov wrote:
James Berry <[EMAIL PROTECTED]> writes:

It seems like Xerces-C 3.0 doesn't have enough visibility to get the
attention it needs to fix build issues. What if we were just to
release the ***mned thing and let those who want to use it contribute
patches to make it build on those platforms they want it to build
on??? I'd love to see 3.0 get out the door, with promise of 3.0.1,
etc as needed to fix build issues, than to never have 3.0 get out the
door.

I don't think it is a good idea to make a release that does not build
cleanly on such a popular platform as GNU/Linux.

Hmm. I don't see that result in the build status? The Linux platforms look to be building. Or do you have information not represented there?

http://wiki.apache.org/xerces/XercescBuildStatus

The only result will
be more people migrating away to other parsers (e.g., Expat and libxml2).
Xerces-C++ already has a reputation of being slow and, putting it
mildly, unnatural to work with. I believe a better way to get more
visibility is to put some effort and ship a quality release.

I want to put out a good release too. But we've had Xerces-C 3.0 basically ready to go for several years now, held up by the apparent build problems on "obscure" compilers ;) I'm just looking for a way out of the log jam. My point is simply that we could wait forever for perfection, or get something out that will take us down the road to perfection.

As I
mentioned in one of my posts to this list, I am prepared to act as
a release manager and push for 3.0 after 2.8.0 is out.

And of course your energy would be appreciated on 3.0 as well... especially as I have precious little available to give beyond a few cheers from the sidelines.

James



-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