OpenFlow Releases

Version	Status	Date	Information	Release Notes	Bugs	GIT	Download
0.9	Planning		Wiki Page	Relase Notes	Trac
0.8.9	Implementation		Wiki Page	Relase Notes	Trac
0.8.2	Released	10/17/08	Wiki Page	Relase Notes	Trac	Git	openflow-v0.8.2.tar.gz
0.8.1	Released	05/20/08	Blog Post	Change Log	Trac	Git	openflow-v0.8.1.tar.gz
0.8.0	Released	05/05/08	n/a	Change Log	Trac	Git	openflow-v0.8.1.tar.gz

For older releases see the Version Archieve

The OpenFlow Specification and the OpenFlow Reference Implementations are available from two different sources:

The life cycle for a new OpenFlow release is:

Planning This happens via a wiki page and discussion on the OpenFlow-dev mailing list. Feature and change requests come from both vendors and researchers, this is meant to be an open process.
Implementation. This happens with developers merging their private Git branches with additions/mods/deletions into the mainline of the master OpenFlow Git repo. Larger, multi-developer features may require temporary branches in the repo. When all the features are added, formal testing begins.
Testing. As a first check, the release candidate is run against our regression suite, which tests individual OpenFlow message types (black_box tests), as well as checks that the sample controller plus the OpenFlow switch act as an Ethernet switch (learning_switch tests). The Wireshark Dissector is hand-verified by checking its output during a run of the black_box tests. In addition, we do feature testing with the release candidate by adding it to whatever apps we're currently running on top of OpenFlow and checking that nothing breaks.
Release. The release is tagged in Git, and posted on the Download page.

Bug fixes releases are released directly after internal testing.