Blame
| 6f02e7 | Samuli Seppänen | 2025-01-29 06:40:08 | 1 | # OpenVPN Beta 2.2 Release Blockers |
| 2 | ||||
| 3 | ## Remaining Trac Tickets |
|||
| 4 | ||||
| 5 | OpenVPN 2.2 beta is technically ready for release except for a few trivial work in progress issues: |
|||
| 6 | ||||
| 7 | - [Ticket 18](https://community.openvpn.net/openvpn/ticket/18) |
|||
| 8 | - [Ticket 20](https://community.openvpn.net/openvpn/ticket/20) |
|||
| 9 | ||||
| 10 | ## Lack of Windows Client Binaries and Signed TUN/TAP Drivers |
|||
| 11 | ||||
| 12 | 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. |
|||
| 13 | ||||
| 14 | **Question:** Who will take care of creating the Windows beta 2.2 packages/installers? |
|||
| 15 | ||||
| 16 | ## Hosting of OpenVPN 2.2 Beta Releases |
|||
| 17 | ||||
| 18 | Where shall we host the OpenVPN 2.2 beta releases? The easiest and least error-prone setup would be the following: |
|||
| 19 | ||||
| 20 | - Host beta releases on **build.openvpn.net**: allows buildslaves to push new builds to the public without manual intervention. |
|||
| 21 | - Provide a direct link to the latest release from **openvpn.net**. |
|||
| 22 | ||||
| 23 | ## Announcing the 2.2 Beta Release |
|||
| 24 | ||||
| 25 | 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. |
|||
| 26 | ||||
| 27 | **Question:** Who will take care of these announcements? |