On Fri, May 28, 2004 at 01:00:31PM -0700, Dan Quinlan wrote: > 1. I took all bugs in the 3.0.0 tracker bug and made sure all have a > milestone release of 3.0.0. Using milestones is much easier to query > and track, especially as the list of bugs grew and grew and grew.
Fine by me. > 2. I added a 3.0.1 milestone. Ok. > 3. I propose we enter Review-then-Commit mode for HEAD on Monday morning > at 0900 UTC. That should be enough time to cycle everything out of > 70_testing.cf, including some network tests that I need to add (NJABL > has a new dynamic list I want us to test) before this weekend. I'd rather not. We have a release plan already, I'd rather stick to it and update the dates. In short, it says we should get everything done, get votes for enhancements before moving to the 3.0 queue, and get the mass-checks started. RTC mode is good for the start/end of the mass-check runs. > 4. All developers and bug editors, please review those bugs that remain > in the 3.0.0 queue (that is, those bugs with a 3.0.0 milestone). We > should change bugs as appropriate to have a 3.0.1 or 3.1.0 milestone. > Here are the general criteria I propose: > > major bugs stay in 3.0.0 > minor bugs move to 3.0.1 > optional/big changes move to 3.1.0 > > Later, things can be moved to earlier releases as code is completed > and fully tested. I'm happy to be more aggressive about tickets, but we need to decide which tickets are which. See below. > 5. We release 3.0.0-pre1 in one week to have more people start testing > it. It already has better accuracy for both FPs and FNs than 2.63. We could put in general scores based on the daily/weekly runs for pre1, btw. Just a thought. Currently open tickets and my comments: 2427 enh Add combined rules file to improve scores on multiple rules 3431 enh [review] feature to add hostname of the remote client to ... 2853 enh [review] Rewrite masses/ (in perl) 3435 enh Support for --long-options for spamc? 1645 enh updated french ruleset I think all of these can be punted. 2427: needs testing. 3431 is pretty much done I think so that should be trivial to get in and close. 2853: good idea, but I think it's too complex for right now. 3435: I thought this was going to be easily straightforward, but it's clearly not, doh. 1645: french rules? needs french mails/results/etc. too complex for now. except for 3431, 3.1.0? 3082 nor auto-whitelist database needs expiry this is really an enhancement, and isn't complete enough for 3.0 imho. 3.1.0. 2037 nor SQL efficiency: keep persistent DB connections also an enhancement, and has no code or anything. 3.1.0. 3169 nor Fix SPF failures I think this is done? 2987 nor Put user config options at top of Conf.pm we're already on the way for this, so may as well finish it. 3438 nor Conflicting API documentation whatever, doco fix, just do it. 3326 nor Bayes db update ignored: Too many open files as far as I can tell, this isn't an SA issue. so far, it's been DB_File, ulimit, and the crazy HTML-taint issue which we all agree shouldn't ever have been possible. I'd be fine closing this out now as WFM. 3059 nor runaway spamd with pyzor (uses 100% CPU and does not return) JM can't reproduce, no response from the submitter for a while. 3414 maj BayesSQLStore schema for PostgreSQL wrong 3415 maj BayesStoreSQL quoting issues with PostgreSQL 3378 nor Bayes SQL: fix possible slow query in nspam_nham_change 3380 nor Bayes SQL: Clearing an empty database burns a user id nee... 3381 nor Bayes: Restoring a backup file with spam_count == 0 and/o... these need to get done. 3378, at least, has a patch already. 3295 maj FORGED_DEF_WHITELIST false positives for Yahoo and Orbitz 3.0.1? -- Randomly Generated Tagline: "All language designers are arrogant. Goes with the territory..." (By Larry Wall)
pgplUiQNK5A7u.pgp
Description: PGP signature
