2016-11-08 1:39 GMT+05:00 Samuli Seppänen <sam...@openvpn.net>:
> Hi,
>
> Here's the summary of today's IRC meeting.
>
> ---
>
> COMMUNITY MEETING
>
> Place: #openvpn-meeting on irc.freenode.net
> Date: Monday 7th November 2016
> Time: 20:00 CET (19:00 UTC)
>
> Planned meeting topics for this meeting were here:
>
> <https://community.openvpn.net/openvpn/wiki/Topics-2016-11-07>
>
> The next meeting has not been scheduled yet.
>
> Your local meeting time is easy to check from services such as
>
> <http://www.timeanddate.com/worldclock>
>
> SUMMARY
>
> agi, cron2, dazo, lev, mattock and syzzer participated in this meeting.
>
> ---
>
> Discussed patchwork:
>
> <http://jk.ozlabs.org/projects/patchwork/>
>
> It was agreed that even the minimal level ("show status of patches on the
> list") would be useful, especially with community LDAP integration. At a
> later point we can implement a more elaborate process such as this:
>
> Patch comes in to openvpn-devel
> Patchwork picks it up
> Test "git apply"
> - Failure -> auto-reject
> - Success -> queue
> Preliminary human review ("feature-ACK")
> - Makes sense -> trigger build test
> - Failure -> auto-reject
> - Success -> code review
> - Does not make sense -> reject
>
> This approach would be DoS/misuse-resistant: starting builds automatically
> from random patches sent to list would be dangerous on many levels.
>
> Mattock will start by setting up patchwork with the minimal feature set,
> as discussed above.
>
> ---
>
> Discussed basic Windows testing, which could be fully automated by
> integrating these two tools together:
>
> <https://github.com/mattock/openvpn-windows-buildtest>
> <https://github.com/mattock/openvpn-windows-test>
>
> The glue would probably more Powershell scripting, along with a Chocolatey
> repository for OpenVPN:
>
> <https://chocolatey.org/>
>
> Wpkg was also mentioned as an option for Chocolatey, but it is less well
> suited for a public-facing repository, as some of its features depend on
> SMB shares.
>
> ---
>
> Discussed OpenVPN 2.4 release schedule. It was agreed to set the deadline
> for 2.4_beta1 to November 16th. That will give us some time to finish the
> final set of really important patches. Any major features that remain will
> be postponed for 2.5. The release date for 2.5_alpha1 could be set to ~6
> months after 2.4.0, so this postponement of features would not be the end
> of the work.
>
> ---
>
> Discussed the only known openvpnserv2 issue:
>
> <https://github.com/xkjyeah/openvpnserv2/issues/10>
>
> Agreed that, if possible, the fix should go in to 2.4.0, but if necessary,
> to a later point release. The fix is important, as it is possible, in
> certain cases, for connectivity to break, if openvpnserv2 restarts a
> connection.
>
> ---
>
> Discussed our systemd unit files, which would be good to have in all
> distros; right now all distros have rolled up their own. Our unit files
> handle clients and servers separately, which has the benefit that it allows
> seamless migrations, as well as fixes some issues with certain Cloud
> providers:
>
> <https://community.openvpn.net/openvpn/ticket/462>
> <https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1580356>
>
> Agi, the Debian package maintainer, will test our systemd unit files and
> report back.
>
> ---
>
> Discussed latest results from Coverity Scan. Our defect average is way
> below industry average. The new "defects" in our current code (as reported
> by Coverity) are not really defects, but more related to coding style.
>
> ---
>
> Discussed OpenVPN 2.3.14 release. The biggest thing missing is
> "block-outside-dns v2". The
block-outside-dns is not supported on WinXP, right ?
> remaining things are fairly minor in comparison. Decided to release 2.3.14
> after 2.4_beta1 is out to keep our focus clear.
>
> --
>
> Full chatlog has been attached to this email.
>
> --
> Samuli Seppänen
> Community Manager
> OpenVPN Technologies, Inc
>
> irc freenode net: mattock
>
>
>
> ------------------------------------------------------------
> ------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
>
>
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
