# OpenVPN Beta 2.2 Release Blockers

## Remaining Trac Tickets

OpenVPN 2.2 beta is technically ready for release except for a few trivial work in progress issues:

- [Ticket 18](https://community.openvpn.net/openvpn/ticket/18)
- [Ticket 20](https://community.openvpn.net/openvpn/ticket/20)

## Lack of Windows Client Binaries and Signed TUN/TAP Drivers

All beta 2.2 packages except *Windows binaries* can be built automatically by Buildbot. Cross-compiling Windows binaries on *NIX* **with** the TUN/TAP drivers is not possible. Therefore, a Windows computer has to be used. Unfortunately, nobody (we know of) in the community has a Windows setup that could be used to build Windows client binaries and/or signed TUN/TAP drivers for 2.2 beta.

**Question:** Who will take care of creating the Windows beta 2.2 packages/installers?

## Hosting of OpenVPN 2.2 Beta Releases

Where shall we host the OpenVPN 2.2 beta releases? The easiest and least error-prone setup would be the following:

- Host beta releases on **build.openvpn.net**: allows buildslaves to push new builds to the public without manual intervention.
- Provide a direct link to the latest release from **openvpn.net**.

## Announcing the 2.2 Beta Release

We also need to officially announce the beta 2.2 release. Any community/company member can send an email to openvpn-devel, openvpn-user, and post to ovpnforum.com (soon forums.openvpn.net). Someone from the company would need to announce the release on Twitter and our web pages.

**Question:** Who will take care of these announcements?