You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 51 Next »

The latest version

  • New Release: On 2005-09-??, SpamAssassin 3.1.0 was released. (historical release schedule: Release310Schedule)

  • New Release: On 2005-06-06, SpamAssassin 3.0.4 was released. [http://mail-archives.apache.org/mod_mbox/spamassassin-announce/200506.mbox/<20050606223631.GG11538@kluge.net> Release Announcement], [http://spamassassin.apache.org/downloads.cgi?update=200506061100 Download now]. Instructions on UpgradingVersion and ["changes304"] available.

  • Release: On 2005-04-28, SpamAssassin 3.0.3 was released. [http://spamassassin.apache.org/downloads.cgi Download now], ["changes303"] notes

  • Release: On 2004-12-16, SpamAssassin 3.0.2 was released. [http://spamassassin.apache.org/downloads.cgi Download now], ["changes302"] notes

  • Release: On 2004-10-22, SpamAssassin 3.0.1 was released. ["changes301"] notes

  • Release: On 2004-09-22, SpamAssassin 3.0.0 was released: [http://mail-archives.apache.org/eyebrowse/ReadMsg?listName=users@spamassassin.apache.org&msgNo=16202 Release Announcement], [http://mail-archives.apache.org/eyebrowse/ReadMsg?listName=users@spamassassin.apache.org&msgNo=16203 Release Notes and Information], UpgradeTo300 notes

New versions

When is the next version of Spam{{`Assassin going to be released? Spam}}`Assassin is an Open-Source project, created by team of volunteer programmers. The exact schedule depends on a number of factors and is hard to predict. The following is the current status. If you are keen to see pre-release versions, keep in mind that WeLoveVolunteers, and there's lots of DevelopmentStuff.

  • Version 3.0.5: Unlikely
  • Version 3.1.1: Soon, but no firm date yet
  • Version 3.2.0: Far off

How are versions numbered?

Versions are denoted using a standard triplet of integers: MAJOR.MINOR.PATCH. The basic intent is that MAJOR versions are incompatible, large-scale upgrades of the API. MINOR versions retain source and binary compatibility with older minor versions, and changes in the PATCH level are perfectly compatible, forwards and backwards.

  • The major version number increments upon significant architectural changes or the achievement of important milestones in capabilities. The minor/mode version number increments as progress is made within a major version.
  • The patchlevel number increments for small sets of changes, providing the most fine-grain timeline of software evolution. Patchlevels increment regularly for internal/development(odd minor level) work, but only increment for external releases when an official update to the previous release version has been tested and packaged.

When a version is almost ready to be released, it is called a "release candidate," (RC), so the version will be numbered something like, "3.0.0RC3." Generally a final version is released within a few weeks of the RC versions.

Keywords: Latest Version Upgrade New Version New Release New Features

CategoryDevelopment

  • No labels