Blame
| 44d14d | flichtenheld | 2026-07-15 12:05:22 | 1 | # Basic info |
| 2 | ||||
| 3 | * Time: Wednesday 15 July 2026 at 14:00 CEST (12:00 UTC) |
|||
| 4 | * Place: #openvpn-meeting channel on !LiberaChat IRC network |
|||
| 5 | ||||
| 6 | # Topics |
|||
| 7 | ||||
| 5bfd39 | flichtenheld | 2026-07-15 13:17:32 | 8 | * **2.7.5 release** |
| 9 | We want to do another release soonish due to some pending security fixes. We're not sure the changes will |
|||
| 10 | be ready for next week, or whether we need another two weeks. Will need to reassess at the start of next week. |
|||
| 11 | ||||
| 12 | * **Amount of open changes in the queue** |
|||
| 13 | Some discussion about the number of open patches (e.g. about 120 open changes in Gerrit). We definitely need to |
|||
| 14 | look into our processes again and how to spread all that work reviewing, testing, and integrating. Likely also a |
|||
| 15 | topic for the 2026 Community Meetup in Paderborn. djpig is working on better documenting the current processes, |
|||
| 16 | see e.g. [1776: Start a new document CODE_CHECKLIST](https://gerrit.openvpn.net/c/openvpn/+/1776) in Gerrit. |
|||
| 44d14d | flichtenheld | 2026-07-15 12:05:22 | 17 | |
| 5bfd39 | flichtenheld | 2026-07-15 13:17:32 | 18 | * **Coordinating big changes** |
| 19 | A related discussion is how to handle big changesets (e.g. currently the multipeer changes from plaisthos and the |
|||
| 20 | oob changes from lev). There was some unhappiness that these changesets are dropped without sufficient context and |
|||
| 21 | that makes it hard to keep track of all the developments. One advise is that developers that want to have big (or many) |
|||
| 22 | changes merged are encouraged to write a mail to the mailing list to provide a "cover letter" for the patch set and |
|||
| 23 | a convenient place to discuss the overall direction without getting bogged down in the discussion of individual changes. |
|||
| 24 | We have lost this practice since not generally using mail-based patchsets anymore. That can be also a good opportunity |
|||
| 25 | to point out dicussions happening in PRs for the RFC document. |
|||
| 26 | ||||
| 27 | # Backlog |
|||
| 28 | ||||
| 29 | - **CVE handling during holidays** |
|||
| 44d14d | flichtenheld | 2026-07-15 12:05:22 | 30 | Due to holidays, temporarily evaluation of CVE and assigning IDs is postponed. This will be for approximately 3 weeks. |
| 31 | Reports will still be able to come in but determining if it's an actual CVE or not and assigning an ID will have to wait. |
|||
| 32 | ||||
| 33 | - **test latency and MTU in openvpn** |
|||
| 34 | A new feature is proposed for adding to master; ability to do latency and MTU tests in the OpenVPN protocol. |
|||
| 35 | Idea is to allow to do a 'best server selection' type of logic, in case there are multiple servers available to connect to. |
|||
| 36 | RFC PR is at https://github.com/OpenVPN/openvpn-rfc/pull/30 and an early initial implementation is available from lev. |
|||
| 37 | ||||
| 38 | - **community meetup 2026** |
|||
| 39 | Coordination is currently taking place here: https://community.openvpn.net/Meetups/2026-Paderborn |
|||
| 40 | The date is around 17 and 18 October, location in Paderborn, Germany. |
|||
| 41 | ordex has volunteered to update and polish the page, fill in some further details. |
|||
| 42 | ||||
| 43 | - **2.7 security audit** |
|||
| 44 | The security audit was completed for 2.7.0 and results are available internally. |
|||
| 45 | We are working to publish this in an official blog post. ordex and novaflash are driving this in OpenVPN Inc. internally. |