Commit f63467

2026-07-22 12:11:42 flichtenheld: -/-
Meetings/2026/2026-07-22.md ..
@@ 6,23 6,9 @@
# Topics
* **Updated: 2.7.6 release**
- We want to do another release soonish due to some pending security fixes. We're not sure the changes will
- be ready for next week, or whether we need another two weeks. Will need to reassess at the start of next week.
-
- * **Amount of open changes in the queue**
- Some discussion about the number of open patches (e.g. about 120 open changes in Gerrit). We definitely need to
- look into our processes again and how to spread all that work reviewing, testing, and integrating. Likely also a
- topic for the 2026 Community Meetup in Paderborn. djpig is working on better documenting the current processes,
- see e.g. [1776: Start a new document CODE_CHECKLIST](https://gerrit.openvpn.net/c/openvpn/+/1776) in Gerrit.
-
- * **Coordinating big changes**
- A related discussion is how to handle big changesets (e.g. currently the multipeer changes from plaisthos and the
- oob changes from lev). There was some unhappiness that these changesets are dropped without sufficient context and
- that makes it hard to keep track of all the developments. One advise is that developers that want to have big (or many)
- changes merged are encouraged to write a mail to the mailing list to provide a "cover letter" for the patch set and
- a convenient place to discuss the overall direction without getting bogged down in the discussion of individual changes.
- We have lost this practice since not generally using mail-based patchsets anymore. That can be also a good opportunity
- to point out dicussions happening in PRs for the RFC document.
+ We want to do another release soonish due to some pending security fixes. But we're not ready this week so
+ it is planned for next week (~ July 29). One of the two security fixes doesn't seem to be worth an embargo,
+ so we decided to handle the review through Gerrit. MaxF will move his PR to there.
# Backlog
@@ 43,3 29,18 @@
- **2.7 security audit**
The security audit was completed for 2.7.0 and results are available internally.
We are working to publish this in an official blog post. ordex and novaflash are driving this in OpenVPN Inc. internally.
+
+ * **Amount of open changes in the queue**
+ Some discussion about the number of open patches (e.g. about 120 open changes in Gerrit). We definitely need to
+ look into our processes again and how to spread all that work reviewing, testing, and integrating. Likely also a
+ topic for the 2026 Community Meetup in Paderborn. djpig is working on better documenting the current processes,
+ see e.g. [1776: Start a new document CODE_CHECKLIST](https://gerrit.openvpn.net/c/openvpn/+/1776) in Gerrit.
+
+ * **Coordinating big changes**
+ A related discussion is how to handle big changesets (e.g. currently the multipeer changes from plaisthos and the
+ oob changes from lev). There was some unhappiness that these changesets are dropped without sufficient context and
+ that makes it hard to keep track of all the developments. One advise is that developers that want to have big (or many)
+ changes merged are encouraged to write a mail to the mailing list to provide a "cover letter" for the patch set and
+ a convenient place to discuss the overall direction without getting bogged down in the discussion of individual changes.
+ We have lost this practice since not generally using mail-based patchsets anymore. That can be also a good opportunity
+ to point out dicussions happening in PRs for the RFC document.
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9