Noel, First off, sorry I kicked off this morning, not a productive thing to do, and I certainly didn't mean to come across so grumpy. Nextly to address the issue at hand..
> My belief is that the POP/SMTP code is close to Release Build status (the > last Release Build was 2.0a3), I agree I've (finally) had a stable build running for a whole day in a live situation, installed from a build built from a clean checkout. Once this has run with no problems for two or three days I'll add my +1. > and that the IMAP code is appropriate for a > contemporanous Milestone Build. Yes, the IMAP can be included in the > Release Build, but anyone actually wanting to use it will have to keep up > with other builds; the Release Build IMAP will be buggy. In the past we've included IMAP (before it was voted out) in an incomplete form and simply described it's provision as early access for testing. The modular nature of James means that I, at least, have no problems with this approach. > As I see it, there are 15 open bugs against James. One thought might be > that those bugs related to a "Stable" feature (and that have enough > explanation to identify) be cleared off to declare a Release > Build (even if > 2.0a3 was released with a number of them open). I believe that a > number of > them are already fixed, and can be closed. I think there will be a number of them that have been "accidentally" addressed, some FOL and some "Works for me". I think we can probably safely defer a number of the remaining bugs, as we have done in the past, depending upon their seriousness. One way would be for someone, (Noel if you feel like it) to check/adjust the seriousness level of each open bug and we can put a threshold in the release plan. (for a vote) > > Additionally, Peter has specifically said he feels that TLS is close to > being stable, and that he'd like it included. My comments relating to IMAP also apply here. > Others have talked about > updating the build process as part of the release plan. I'm not sure what is required, but believe this should be defered until the release is made, as it primarily affects cvs users, the downloads work fine. (IMHO) Finally.. I'd add that the whole xdocs need to be reviewed to make sure they reflect changes made since 2.0a3, but I'll tackle this one myself. d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
