References: <20161108124506.32559-1-gert@...1296...> <201611092014.uA9KErZf048132@...2054...> <8feec195-c9ed-a0bb-31c5-459bf9757ce6@...68...> <20161111221004.GC28918@...1296...> From: Matthias Andree Message-ID: Date: Sat, 12 Nov 2016 05:43:56 +0100 MIME-Version: 1.0 In-Reply-To: <20161111221004.GC28918@...1296...> Subject: Re: [Openvpn-devel] [PATCH applied] Re: Repair topology subnet on FreeBSD 11 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable To: "openvpn-devel@lists.sourceforge.net" Am 11.11.2016 um 23:10 schrieb Gert Doering: > I might be tempted to do a quick 2.3.14 release in between - there's two > important platform fixes in that branch now (FreeBSD and OpenBSD topology > subnet :-) ) and Lev's recursive routing patch. Add to that the windows > block-outside-dns patch that I hope to be testing this weekend, and it's > worth a minor bugfix release... at least "before January". Well, for me to update the FreeBSD port, mid December 2016 would be cool for anything (2.3.14, or 2.4.0, or both) due to the before-xmas-madness and to have like two weeks for smoke testing. On the other hand, we're not Debian or Ubuntu, and the FreeBSD ports-secteam (who own the stable "quarterly" ports branch) take a rather pragmatic or management approach than drive their principles and policies home... Also, since the FreeBSD stable ports branches follow a three-months-lifetime scheme, anything we miss in December will go in in April 2017 rather than January, and it's also easy enough to update OpenVPN to the ports HEAD branch if needed ahead of time by some user. While not formally supported, it works for OpenVPN. Bottom line, give Debian the priority, and while it would be nice to have for FreeBSD, no need to rush.