----- Original Message -----
From: "Noel J. Bergman" <[EMAIL PROTECTED]>
> > There are in my mind a number issues with the current code.
> > There are parts of refactoring that make things difficult
> > as we go forward. I will be happy elaborate post tests.
>
> Why don't you elaborate now?  What specific technical issues do you have
> with the current code?

It is a distraction. I expect to be done with tests and all fixes in 1 week
or at most 10 days. Shorter say 3 days if there an aggressive need to hurry
up and get 2.1.1 out.

I could say a few things and start a email chain and what I say may not be
complete as I haven't tested sufficiently.

>
> > This is exactly what happenned in the past when I had patches but
> > before I could patch, there were untested pre-emptive checkins.
>
> Again?  We keep going over this.  There were no check-ins to NNTP for many
> months despite a raft of defects in the code.
>
> As for the patches I have, I have submitted them for review, I do plan to
> test them, and if they work, I see no reason why we should not use them.
> But I am also willing to see what you have in mind.

The raft has mostly been due to refactoring. As a comparison the first
checkin of NNTP was working better than current code.
All I have in mind is that regressions should be fixed and there should
verifiable tests. That would make everybody on this list more sane and help
avoid regresssions in future. I have spent the new year holiday thinking
about a good testing strategy and researching a few libraries. I would not
have done that if I felt we should just do the fixes. It was working
earlier, got broken, caused a lot of ache, don't want it repeated. Let us
take this as a learning experience and not rush to fix things.

If the time frame offered is not good enough or you think I am being
unreasonable please go ahead, otherwise I'll be happy to get NNTP working
with tests that I belive that would please everybody here and James
community.

Harmeet


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

Reply via email to