04/20: DONE - get bugzilla prioritized and either close/punt stuff we're not going to get to to 3.1. We will need to get agressive about some tickets -- for instance: we can't avoid all FPs, so if they don't happen often and if it's not easy to fix, accept it, close the ticket, and move on. Get open 3.0 tickets down to around 50.
04/22: ACTIVE - feature freeze -- no more adding enhancements to 3.0 w/out vote 04/28: DONE - do bug squashing event for as many remaining open tickets as possible. I assume there'll still be a few major ones open. 05/12: all tickets should be finished and closed. all testing rules should be promoted or removed. do testing to make sure the mass-checks will be smooth. 05/07: warn people that mass-check runs will be starting shortly 05/17: announce mass-check run 1 (sets 0 and 1), run until 05/24. enter R-T-C mode. 05/26: generate scores, etc. 05/31: announce mass-check run 2 (sets 2 and 3), run until 06/11. 06/13: generate scores, etc. 06/15: release 3.0.0rc1 -- fix bugs that come up, do polishing, etc. release other 3.0.0rc as appropriate. 06/30: planned release of 3.0.0-final -----Original Message----- From: Matt Kettler [mailto:[EMAIL PROTECTED] Sent: Friday, May 28, 2004 1:37 PM To: [EMAIL PROTECTED] Subject: Re: next release? At 01:26 PM 5/28/2004, Florin Andrei wrote: >Is there a timeframe for releasing the next stable version? When it's done? The last estimate I heard was one Theo posted in Feburary, and that claimed "sometime in may". However, looking at the bugzilla, there's still several outstanding bugs to fix before 3.0 http://bugzilla.spamassassin.org/show_bug.cgi?id=3208 Once they get all the bugs fixed and freeze the code, it will take about 3 weeks to do the mass-checks. So, on pure speculation, I'd venture to guess early or mid-July. However, the developers of the project should have have a better feel for this than I do. (ie: Theo, Justin, Daniel, etc.)
