Changes between Version 1 and Version 2 of Topics-2023-02-15

Timestamp:

02/15/23 13:00:54 (15 months ago)

Author:

OpenVPN Inc.

Comment:

--

Topics-2023-02-15

@@ -10 +10 @@
 * **Planning to have a new release of OpenVPN 2.6 around March 8th.**
 
-* **2.6 release - any new feedback, anything vital?**\\''anything new to discuss?''
+* **2.6 release - any new feedback, anything vital?**\\''a DCO with BSOD on systems with legacy standby modes, lev__ reproduced and fixed it.\\azure vpn gateway has their own implementation of openvpn that is incompatible with 2.6.\\lev__ contacted them and offered to help to find and resolve the problem.\\we should prepare an I005 release today and get that pushed out.''
 
-* **License amendment for OpenVPN2 to solve openssl/mbedtls licensing issues**\\''current status is that we know for sure from legal expert that an exception addition is necessary.\\there is a draft that has been refined based on feedback from community and company members.\\plaisthos and dazo have been working on refining the proposal and should be able to present something in this meeting.''
+* **License amendment for OpenVPN2 to solve openssl/mbedtls licensing issues**\\''current status is that we know for sure from legal expert that an exception addition is necessary.\\a refined and lawyer approved proposal is ready to be sent to the mailing list.''
 
 * **Hackathon blog post on openvpn website is ready**\\''this is about the hackathon in delft in november.\\community review is requested - if it's good to go it will be published.''
@@ -20 +20 @@
 * **Review DCO-for-Linux release status**\\''working on making control packets go through transport socket instead of netlink. easy for udp, not so easy for tcp.\\looks like ordex will have this change ready for the upcoming 2.6.1 release. we'll rename dco module to ovpn-dco2 then.\\then next item is TCP notification missing under heavy load bug. will retest after control channel moved to socket.''
 
-* **Status of PoC using Gerrit for code review.**\\''the proof of concept is online. stated goals are:\\replace patchwork. all mailing list conversation around a patch visible in gerrit. reviews in gerrit entirely.\\plus, see if a patch would break stuff (like, this patch is for windows but breaks linux compilation)\\d12fk and uddr will work together on getting the email list patches into gerrit, and take it from there.''
+* **Status of PoC using Gerrit for code review.**\\''gerrit proof of concept is online.\\goal seems to have settled on - we want to keep existing mailing list since not everyone will be using gerrit. but gerrit will add easier review abilities.\\so gerrit has to send emails to mailing list, pick up patches from mailing list, and review responses to emails sent to mailing list should feed also into gerrit\\uddr will set up a poc with dummy repo so we can start testing out some email functionality of gerrit.''
 
 * **Website release process woes**\\''work started on an API to allow updates at any time on main website for the community downloads section.''