> 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. > --
#2: Get the bug database real. There's only 15 bugs total listed against James. Not in the database is the NNTP break from earlier this week, nor is the POP3 file store bug in there. The patch for the NNTP break is not in there either. The query I used is: http://issues.apache.org/bugzilla/buglist.cgi?bug_status=CLOSED&bug_status=N EW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emai lassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=incl ude&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&produ ct=James&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_typ e=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&ke ywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=bugs.b ug_status%2C%20bugs.priority%2C%20bugs.bug_severity Once there's a realistic set of bugs, realistic planning for 1.2.1 can take shape. 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]>
