Serge,
I also understand Harmeet's point that code shouldn't regress. Oh well,
$#1t happens and from time to time, code regresses. It is the personal
attack that I can (and we must) do without.
There is only one responsible party. His name is James. If there is a bug,
fine. James will fix it. James creates the code, James supports the code,
and if necessary James fixes the code.
Yes, you did open the door with the file respositories issue. And, yes, the
fact that it would be considered a showstopper should have been raised much
sooner. However, to many of our users it appears that it was a critical
problem, and so we voted to fix it.
I agree with you that NNTP doesn't represent a show stopper for v2.1
release. We should get v2.1 out to our user community, and unfreeze the
codebase. In fact, I believe that there are other patches pending for
non-showstopper defects, and we can roll more of them into a
mid-to-late-January update. I've said before that we ought to be releasing
more regularly.
Defects occur. They can and must be tolerated. What cannot be tolerated
are personal attacks.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
