compared with
Current by Thor Henning Hetland
on Oct 31, 2020 21:56.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (17)

View Page History
Whydah stable releases use the name version number as the release number.
* Latest stable release: *Whydah 2.5*

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* will be version *2.0.1*, then *2.0.2*, as necessary. A bug fix release replaces the previous stable release.

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.

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.6 - Release Log] (Oct 2020)
* [Whydah 2.5 - Release Log] (August 2018)
* [Whydah 2.4 - Release Log] (December 2017)
* [Whydah 2.3 - Release Log] (September 2017
* [Whydah 2.2 - Release Log] (April 2017)
* [Whydah 2.1 - Release Log] (December 2015)
* [Whydah 2.0 - Release Log] (October 2014)
* -[Intermediate, pre 2.0 releases]-
* -[Pre 1.0 releases]-

-----
{section}
{column}

h3. Preview Versions

* "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.
* [Whydah 2.* - Release log]

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

h3. Latest beta release is Whydah 2.0-beta-2
See [Whydah 2.0 - 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 alfa release is Whydah 2.0-alpha-16
See [Whydah 2.0 - Release Log]
{column}
{column}

h3. Planned releases

* [Whydah 2.7 - Release Log] (November 2020+)
* [Whydah 3.0 - Encrypted tokens and high security applications]
* [Whydah 4.0 - DEFCON and handling installations under attack]

{column}
{section}