When is the next version of SpamAssassin going to be released?
Short answer: When it's ready.
Longer answer: Probably sooner if you help.
Because of the way SpamAssassin's default scores are determined, it generally takes a lot longer to release major versions (i.e. x.x.0 or x.x0) than we'd like. Here are the major steps we take before a release.
All the bugs that we agree need to be done for the next release need to be fixed. (For 3.0.0, you can look at [http://bugzilla.spamassassin.org/show_bug.cgi?id=3208 bug 3208], you can also query for bugs where the target milestone is 3.0.0) 2. We need to enter a rule freeze and run 3 mass-checks (MassCheck) and perceptron runs to optimize the rule scores. Since these mass-checks require volunteers from around the world to run SpamAssassin over very large volumes of mail, these generally take about a week each. 3. We need roughly two weeks of testing to eradicate any major bugs that creep in. (It's difficult to test SpamAssassin before the mass-checks are done because the scores are generally quite poor, making it relatively unusable on real mail.) During this time we will generally distribute release-candidate (RC) releases for wider testing. Test these! 4. If all goes well, we release.
Minor releases tend to have a lot shorter release schedule as only important bug fixes happen and the scores (usually) stay the same.
How can you help? Simple. Fix bugs. Log into [http://bugzilla.spamassassin.org Bugzilla] and browse through the bugs that are holding up the release. Fix them and attach patches to the bugs. (You may need to also fill out and send in a [http://www.apache.org/licenses/#clas Contributor License Agreement] before we can use your patch.) Also, WeLoveVolunteers.
(DuncanFindlay)
Schedule for SpamAssassin 3.0
The following schedule was first posted by TheoVanDinter to the SpamAssassin development mailinglist on April 21st 2004. He wrote:
Here's what I came up with. These are meant to be guidelines, not
hard dates. This schedule has a release in 10 weeks. I'd really like
to beat that. Depending on schedules, we can probably move up the code
related work. The release related stuff is pretty much the amount of
time it usually takes though.
Code Related
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: feature freeze – no more adding enhancements to 3.0 w/out vote
04/28: 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.
Release Related
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