Mailing List Archive: [Spamassassin Wiki] Update of "NextRelease" by JustinMason

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.

The following page has been changed by JustinMason:
http://wiki.apache.org/spamassassin/NextRelease

------------------------------------------------------------------------------
= The latest version =

+ * '''New Release:''' On 2005-09-??, Spam``Assassin 3.1.0 was released. (historical release schedule: Release310Schedule)
- Spam``Assassin version 3.0 delivers many new features including support for sender authentication using the Sender Policy Framework (SPF), checking for web links of known spam advertisers, a modular plugin architecture, improved SQL database support for storing user data in server installations, and improved email classification.
-
* '''New Release:''' On 2005-06-06, Spam``Assassin 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, Spam``Assassin 3.0.3 was released. [http://spamassassin.apache.org/downloads.cgi Download now], ["changes303"] notes
@@ -20, +19 @@

* Version 3.0.5: Unlikely

- * Version 3.1.0: scheduled: Release310Schedule.
+ * Version 3.1.1: Soon, but no firm date yet
+
+ * Version 3.2.0: Far off

= How are versions numbered? =

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.

The following page has been changed by JustinMason:
http://wiki.apache.org/spamassassin/NextRelease

The comment on the change is:
it's lowercase

------------------------------------------------------------------------------

* 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.
+ 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.

----------