View Source

*Whydah stable releases use the name version number as the release number with the .Final appended.*

* Latest stable release: *Whydah 2.0.Final*

A bug fix release follows a stable release, when necessary. Bug fix releases add a sequence number to the product release number. Thus, the first bug fix release for Whydah 2.0.Final will be version 2.0.1.Final, then 2.0.2.Final, as necessary. A bug fix release replaces the previous stable release.

Bug fix releases are follow-ons to stable releases. Bug fix versions automatically start at stability "rc", reflecting the fact that only localized bug fixes are expected to be included in such a release. Once all desired bug fixes are in place, a stability vote (to "stable") is followed by a release vote.


h3. Releases

* [Whydah 2.0 - Release Log]

h3. Preview Versions

* [Whydah 2.1 - Release log]


* *_alpha_* versions are not stable; the represent functionality in flux; classes and methods may be renamed or otherwise refactored between releases.
* *_beta_* versions occur once main functionality is complete; they exist to fix bugs in both old and new functionality, and fill any gaps in functionality.
* *_rc_* versions are "release candidates"; the functionality should be solid; the point of a release candidate is to get wide exposure to the new codebase to ensure that the final release is free of bugs.

h3. Latest release candidate is Whydah 2.0-rc-5
See [Whydah 2.0 - Release Log]

h3. Latest beta release is Whydah 2.0-beta-2
See [Whydah 2.0 - Release Log]

h3. Latest alfa release is Whydah 2.0-alpha-16
See [Whydah 2.0 - Release Log]




-----

h3. Old releases

* -[Intermediate, pre 2.0 releases]-
* -[Pre 1.0 releases]-