Harmeet,
I really don't see any point in delaying this release further to fix NNTP.
If that protocol is still broken, I would just as soon remove it from the
distribution until someone has time to do it properly.
Personally, I don't use NNTP with James, so I can't verify your unspecified
claims at this time, but if they are correct, let's just take NNTP out until
it can pass a protocol compliance test.
What specifically ARE the problems? Basically your message, by your own
admission, is a rehashing of old wounds without telling us what bugs you
think are present in the current code.
If there are some defects, there have been MONTHS for someone to work on
NNTP. No one did. I proposed removing it before now, so if it still isn't
working right, let's just move the thing to proposals/ (or simply remove the
entry from config.xml entirely) and be done with it for now. If you want to
prepare patches for NNTP based upon the current code base, please do so, and
we can re-enable NNTP in a 2.2 update, perhaps in late January. I'll even
start using NNTP internally, so that I can check it, too.
As for your name, we've already agreed that ALL author tags will be removed
from the code. This is community project, and everyone ought to take
responsibilty for all aspects. Why is why I do find it annoying that you
would post a message rehashing old wounds, disparaging other contributors,
and not even mention the specific bugs that you feel are present. I don't
find any of that beneficial to building our community. Your note could (and
should) have been a matter of fact reporting of specific bugs that need to
be fixed.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
