Harmeet Bedi wrote:
----- Original Message -----
From: "Noel J. Bergman" <[EMAIL PROTECTED]>

I think that you just have a very hard time not pointing fingers.
..

to point fingers at.  Ego-less programming.  If a change breaks something,
the change is broken, NOT THE CHANGER.


Noel if there are many regressions caused by one developer, it is the right
thing to point fingure and expect improvements. I will be happy if the
person promises to test more in future.

If there are number of changes(as half a dozen protocol server regressions
indicate) the process is to have a proposal not checkin into head. Checkin
into head impacts everyone and causes 11th hour headaches for the release.

Harmeet
The scope of this change doesn't seem clear and doesn't seem small. So I'm -1 to any fixes/changes to NNTP for the 2.1 release at this point. Accordingly I'll +1 the change to disable NNTP since it won't be working.

--
Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to