Hi Andy, >Like I'm supposed to notice changes to a single file >in CVS... Please.
To be fair, this file hasn't changed since Lisa added it. And she only added it *after* posting it to this list. So the idea that 2.1.0 was due some time around now has been a known--and debatable--item in the public domain for quite a while... >Moving to a 2.x.0 release is a BIG DEAL. That's the >place where API changes are acceptable, not in a sub- >point release (despite what we've been doing lately). >That's why I wanted some serious discussion on my API >change *before* this release. And that's why I posted >my query to the mailing list well ahead of time. And >now I have to wait until another point release?!?! Nothing saying the next release can't be called 2.2.0. And, if the change is beneficial enough (and you don't mind the trivial work of publishing the release), there's also nothing saying it can't necessarily fall quickly on the heels of this one. All that said, I can well understand your chagrin. All I can say is that we should have sent a warning, and encourage you to ping the list if you're curious what other folks in the community have in mind. Cheers, Neil Neil Graham 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]
