Blame
| dc3121 | novaflash | 2025-11-05 13:53:08 | 1 | # Basic info |
| 2 | ||||
| 3 | * Time: Wednesday 5 November 2025 at 14:00 CEST (12:00 UTC) |
|||
| 4 | * Place: #openvpn-meeting channel on !LiberaChat IRC network |
|||
| 5 | ||||
| 6 | # Topics |
|||
| 7 | ||||
| 8 | - **Updated: Release 2.7** |
|||
| 9 | OpenVPN 2.7 release candidate 1 was released 31st of October. |
|||
| 10 | There were some reports of bugs and issues, which are being fixed and prepared for the rc2 release. |
|||
| 11 | ||||
| 12 | - **New: Release 2.6.16** |
|||
| 13 | Some of the issues also affected 2.6 code. |
|||
| 14 | So a 2.6.16 release seems prudent, to coincide with similar/same fixes done in 2.7rc2. |
|||
| 15 | ||||
| 16 | - **Updated, closed: wolfSSL license changed from gplv2 to gplv3** |
|||
| 17 | The release notes of wolfSSL indicate the license changed to GPLv3. |
|||
| 18 | This basically makes wolfSSL incompatible in regards to licensing with OpenVPN, because OpenVPN is GPLv2 licensed. |
|||
| 19 | After a discussion between maxF, plaisthos, from OpenVPN community, and people from wolfSSL, a conclusion was reached. |
|||
| 20 | wolfSSL believes that an exception to allow linking wolfSSL with OpenVPN is sufficient. They will implement such an exception in their license. |
|||
| 21 | For us this means the topic is closed. |
|||
| 22 | ||||
| 23 | - **New: community meetup 2026** |
|||
| 24 | Tentatively in Paderborn, Germany. |
|||
| 25 | ||||
| 26 | - **forums situation** |
|||
| 27 | minx from OpenVPN Inc. originally set up flarum and started migration process, but he left the company before completion. |
|||
| 28 | Now we have eduardo at OpenVPN Inc. who is taking a look and he managed to get migration working. |
|||
| 6ab61a | novaflash | 2025-11-12 12:53:35 | 29 | He suggests some further migration testing, and to then plan a hard cutover date. |
