----- Original Message ----- From: "Noel J. Bergman" <[EMAIL PROTECTED]>
> > Apply the NNTP Fixes (list, authinfo and character conversion in headers > are > > the necessary fixes) on a good version. Move it to new service model. Keep > > the current NNTP code as is in proposals area. Move javadocs etc and all > > other improvements post 2.1. > > This is doable in one day and very safe to do. > > It appears that your proposal is to revert the NNTP code from the modified > version to the Harmeet version, and then reapply selected changes. This is one of 2 proposals of fixing this. I think it is safer but not the only way. The other way was 'There is a known good version(2.0) and bad version(2.1). If anyone wants to address this, do a network trace and see the diff.' Alternatively....<the proposal above> You have indicated that it is already fixed. I will test more tonight and send any additional fixes to the list. I had decided to wait for 2 days, and will start looking at wire level(protocol developer) rather than user level today and confirm more. I also plan to test with Netscape and KMail. Testing and fixing bugs as regressions are found is the right thing to do. > changes for v2.1.1. I do not feel comfortable with that degree of change in > code that is supposed to be shipping. Actually the code changes are not much. To the order of ~ 25 lines on a working codebase. Code moving to proposals is not lost. If no one else does, I can promise to make sure I copy the changes over after 2.1. Would fixing in the current codebase in a specific manner be ok. I think it is less safe, but with enough testing it should be possible to weed out any issues. Harmeet -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
