By the way, here's my: +1 vote for option A. But I wanted to see what the rest of the community thought, which is why I was asking.
---- scott boag wrote ---- > So none of my reasons really have anything to do with Xerces 2.x... I just OK, so the real issue, as Scott notes, has nothing to do with the new code/performance work. The real issue for me is: should we bother shipping a real Xalan 2.2 point release with Xerces 1.x, or should we just update to Xerces 2.x right now? In theory, it's no big deal, because in theory if you configure everything properly you can compile and run current Xalan CVS with either version of Xerces. In reality, of course, it's a minor hassle to switch between Xerces versions, and we don't even have the final Xerces release yet. Plus there are a few more current test failures with Xerces 2.x than 1.x, although we'll be addressing those soon obviously. Plus the whole fact that it's a "x-dot-oh" release of the parser. I guess the question is: is anyone waiting for a point release of Xalan and is most interested in stability and wants to stay on Xerces 1.x; or, does everyone here simply want the latest and greatest of everything, full speed ahead, let's get 2.x's all around? (As a long-time quality engineer, I'm horrified at the thought of plunking in a bunch of new stuff plus a completely new parser version at the same time. Then again, I've long come to realize that I live in a world of developers who often see things differently... 8-) - Shane ===== <eof aka="mailto:[EMAIL PROTECTED]"; .sig="2002 The palindromic year 2002"/> __________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/
