I'm going to draft a release plan for 1.2.1 to see if it might help the next
release go smoothly.
First item--what's going to be new in the release. Two items so far are:
--Expand NNTP test suite, hopefully they can mostly be automated.
--
> And was expected in October. According to you, this is such a obvious issue
> that any client test in that time frame should have shown it. Apparently,
> our users don't use NNTP, otherwise didn't encounter this issue, or didn't
> care enough about NNTP to report it. Clearly, though, James needs a
> comprehensive test suite to aid in testing (regression and otherwise). You
> can add this as another test case.
>
> At some point you have to freeze the code, test it, and keep it closed so
> that you don't have to go back through testing all over again. We should
> not take so long to get out a release, and we should be able to put out bug
> fix releases as necessary.
>
> Actually, there are other less critical flaws in NNTP, one of which is in
> Bugzilla. I believe that fixes exist and are pending the v2.1 release. So
> the quicker we ship this update, the quicker we can get to other issues.
Matt Bishop
[EMAIL PROTECTED]
"We are all here on earth to help others. What I can't figure out is what
the others are here for."
- W. H. Auden
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
