Blame
| f92b15 | novaflash | 2026-10-21 12:11:25 | 1 | # Basic info |
| 2 | ||||
| 3 | * Time: Wednesday 21 October 2026 at 14:00 CEST (12:00 UTC) |
|||
| 4 | * Place: #openvpn-meeting channel on !LiberaChat IRC network |
|||
| 5 | ||||
| 6 | # Topics |
|||
| 7 | ||||
| 8 | - **Updated: community meetup 2026** |
|||
| 3d6cae | novaflash | 2026-10-21 12:39:51 | 9 | The community meetup has concluded. One of the main takeaways was a potential for 2.8 release in Q1 2027. |
| f92b15 | novaflash | 2026-10-21 12:11:25 | 10 | Meeting notes here: https://community.openvpn.net/Meetups/2026-Paderborn |
| 11 | The location for the next community meetup is set to Zagreb. |
|||
| 12 | ||||
| 3d6cae | novaflash | 2026-10-21 12:39:51 | 13 | * **Updated: 2.7.x release** |
| 14 | Version 2.7.9 is planned for 4 November. |
|||
| 15 | ||||
| f92b15 | novaflash | 2026-10-21 12:11:25 | 16 | # Backlog |
| 17 | ||||
| 18 | * **Updated: 2.7.x release** |
|||
| 19 | Originally 2.7.8 was planned for last week, but a last moment fix for Windows DCO driver made us decide to postpone till today. |
|||
| 20 | 2.7.8 with the Windows DCO driver update will go out today. |
|||
| 21 | Version 2.7.9 is now planned for 4 November. |
|||
| 22 | ||||
| 23 | - **test latency and MTU in openvpn** |
|||
| 24 | A new feature is proposed for adding to master; ability to do latency and MTU tests in the OpenVPN protocol. |
|||
| 25 | This would allow for a client to for example select the best available server based on test results. |
|||
| 26 | This is currently under review: https://gerrit.openvpn.net/q/topic:%22oob-server-probe%22 |
|||
| 27 | The design document is here: https://github.com/lstipakov/openvpn/blob/server-probe-design/design-server-probe.md |
|||
| 28 | ||||
| 29 | - **2.7 security audit** |
|||
| 30 | The security audit was completed for 2.7.0 and results are available internally. |
|||
| 31 | We are working to publish this in an official blog post. ordex and novaflash are driving this in OpenVPN Inc. internally. |
|||
| 32 | ||||
| 33 | * **Coordinating big changes** |
|||
| 34 | A related discussion is how to handle big changesets (e.g. currently the multipeer changes from plaisthos and the |
|||
| 35 | oob changes from lev). There was some unhappiness that these changesets are dropped without sufficient context and |
|||
| 36 | that makes it hard to keep track of all the developments. One advise is that developers that want to have big (or many) |
|||
| 37 | changes merged are encouraged to write a mail to the mailing list to provide a "cover letter" for the patch set and |
|||
| 38 | a convenient place to discuss the overall direction without getting bogged down in the discussion of individual changes. |
|||
| 39 | We have lost this practice since not generally using mail-based patchsets anymore. That can be also a good opportunity |
|||
| 40 | to point out dicussions happening in PRs for the RFC document. |