> > As a courtesy, I'll reply to this note off-list. > Just as it was getting interesting :)
The interesting part of the discussion is the one that we ought to be having; specifically what needs to be done to put out a Release Build of James v2.1 for the benefit of the user community. I'm using the Jakarta terminology for builds (q.v. http://jakarta.apache.org/site/binindex.html). My belief is that the POP/SMTP code is close to Release Build status (the last Release Build was 2.0a3), 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. 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. Additionally, Peter has specifically said he feels that TLS is close to being stable, and that he'd like it included. Others have talked about updating the build process as part of the release plan. --- Noel bugs: http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSI GNED&bug_status=REOPENED&email1=&emailtype1=substring&email2=&emailtype2=sub string&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=No w&chfieldvalue=&product=James&short_desc=&short_desc_type=allwordssubstr&lon g_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwor dssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&val ue0-0-0=&cmdtype=doit&order=%27Importance%27 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
