Whydah Releases

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.

Releases

Whydah 2.0 - Release Log

Preview Versions

[Whydah 2.1 - ApplicationModel and Administration APIs - 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.

Latest release candidate is Whydah 2.0-rc-5

[Whydah 2.1 - ApplicationModel and Administration APIs - Release log]
Whydah 2.0 - Release Log

Latest beta release is Whydah 2.0-beta-2

[Whydah 2.1 - ApplicationModel and Administration APIs - Release log]
Whydah 2.0 - Release Log

Latest alpha release is Whydah 2.0-alpha-16

[Whydah 2.1 - ApplicationModel and Administration APIs - Release log]
Whydah 2.0 - Release Log

Planned releases

[Whydah 2.2 - Encrypted tokens and high security applications]
[Whydah 2.3 - DEFCON and handling installations under attack]