Aaron Stone wrote:
Hans Kristian Rosbach <[EMAIL PROTECTED]> said:
I'm thinking it might be better to release 2.0.2 if we don't get
response from the bug reporters soon. I don't think there are any
regressions the to-be 2.0.2, so it should only be better than
what we recommend people use today.
I agree that 2.0.2 should go out ASAP. We can include some type of NEWS
(e.g. website posting and the freshmeat mini-changelist)...
"The looping bugs found in previous 2.0 releases should now be resolved,
but we do suspect that one last loop still lurks in the IMAP server."
Or something to that effect ;-)
Sound good to me. Any new bug that is a regression from the previous
point release should hold up release, but that's not what we have here.
We have pre-existing bugs that have recently been identified. If there
are no known regressions from 2.0.0, or 2.0.1, then these bugs are not
grounds for holding up the 2.0.2 point release.
