could you guys vote? I reckon, since it's part of an official release plan, we need 3 committer +1's (mine plus two more).
--j. Daryl C. W. O'Shea writes: > Sounds like an alright schedule to me. It'd be nice to get away with a > single RC, but I hope that we have enough people test it that we end up > doing a second one. :) > > Daryl > > > Justin Mason wrote: > > ping -- anyone there? > > > > --j. > > > > Justin Mason writes: > >> Happy new year! New year, time for a new major release since we missed > >> one in 2006 ;) > >> > >> I think the 3.2.0 bugs list has most of the major ones off the list, and > >> the remaining either (a) don't need to be done for 3.2.0 necessarily or > >> (b) will probably be doable in the month or whatever between now and > >> release, in parallel with rescoring (feel free to shout if this is not the > >> case ;). > >> > >> I've created http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5270 to > >> track the rescoring task. > >> > >> First step, I think, is to define a schedule. How does this sound? > >> (based approximately on what we did for 3.1.0: > >> http://wiki.apache.org/spamassassin/Release310Schedule ) > >> > >> - T + 0 days: announce a heads-up mail. clean up our corpora, get ready > >> for mass-checking, try out mass-check to spot any big memory leaks or > >> whatnot, fix remaining bugs that affect mass-checks (esp bug 5260!), > >> get people signed up, enable all rules in svn. > >> > >> - T + 1 week, around a Thursday or so: start --bayes --net mass-checks; > >> move to C-T-R. > >> > >> - T + 3 weeks, a Monday or so: hopefully finish mass-checks, bugs > >> allowing ;) (note that includes two weekends.) > >> > >> - T + 3 weeks: perceptron runs, voting on new proposed scores, etc > >> > >> - T + 4 weeks and a bit: hopefully ready to release > >> > >> > >> Interesting URLs for what happened in the 3.1.0 rescoring: > >> > >> http://wiki.apache.org/spamassassin/Release310Schedule > >> http://wiki.apache.org/spamassassin/RescoreMassCheck > >> http://wiki.apache.org/spamassassin/RescoreDetails > >> http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4505 > >> > >> > >> Here are the remaining 3.2.0 bugs fwiw, apart from bug 5270 (rescoring): > >> > >> 21 bugs found. > >> ID Sev Pri Summary > >> 5155 maj P1 "make install" always attempts to write to > >> /usr/local/lib... > >> 5146 nor P1 remove rule description translations out of > >> SpamAssassin ... > >> 5269 blo P2 may need to have separate mirror sets for > >> differing versi... > >> 5235 maj P2 SPF_FAIL on SMTP-authenticated mail relay > >> 4493 enh P2 add pre-tokenize text munge to learner > >> 4820 maj P3 The code for creating a new userstate_dir is > >> severly broken > >> 4653 min P3 bayes_pg.sql syntax error for old versions of > >> PgSQL (7.4.x) > >> 5260 maj P5 Memory leak persists in 3.2 DNS usage > >> 3563 nor P5 Odd errors if tieing Bayes DB while learning... > >> 4078 nor P5 Windows Hebrew encoding in subject not detected > >> 4332 nor P5 PMS->{redirect_num} unused / obfu redirection not > >> included > >> 4435 nor P5 Progress meter doesn't handle time left when it's > >> in the ... > >> 4598 nor P5 If DNS set available and it's not, hard failure > >> occurs > >> 4717 nor P5 EnvelopeFrom option should be documented > >> 4747 nor P5 Problems with EnvelopeFrom auto-detection > >> 4999 nor P5 spamd --auth-ident trivial to bypass > >> 5110 nor P5 EXTRA_MPART_TYPE fires on valid multipart/related > >> 5185 nor P5 Bayesian learning uses different message checksums > >> during... > >> 5257 nor P5 push out autolearning thresholds for 3.2.0 > >> 4770 min P5 use ASN data as Bayes token > >> > >> --j. > >
