View Source

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

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] (Planned Q1 2019)
* [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)

-----
{section}
{column}

h3. Preview Versions

* [Whydah 2.* - 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.5-rc-1
* [Whydah 2.5 - Release Log]



{column}
{column}

h3. Planned releases

* [Whydah 3.0 - Encrypted tokens and high security applications]
* [Whydah 4.0 - DEFCON and handling installations under attack]

{column}
{section}