Hi, Il 01/11/2016 13:10, Gert Doering ha scritto: > Hi, > > On Mon, Oct 31, 2016 at 11:55:08PM +0100, David Sommerseth wrote: >> How long will users be willing to wait? I'd be really surprised if 2.4 >> is out the door before Christmas 2016. When also considering we've said >> that 2.4_alpha was soon ready for about 1 year or so before it really >> got released, I'd even say I am overly optimistic. > > If we could spend our time on a somewhat focused work on 2.4, instead > of exhausting ourselves discussing feature backports to 2.3, this could > happen faster. > > And more *focused* work: less rounds of review, buildbot explosions, etc., > which eats up everyone else's precious time.
It would be good to: 1) Catch the issues before buildbot In my recent INSTALL-win32.txt removal patch the breakage could have been avoided if I had been less sloppy and had actually tried to build the thing before sending in the patch. A basic "make check" goes a long way, but I intend to de-bashify the Vagrant integration soonish, so that we can merge it. This should make it easier for developers to catch runtime errors before sending in patches: <https://github.com/OpenVPN/openvpn/pull/45> 2) Have buildbot catch issues before code is in Git "master" This could be solved by tracking an "experimental" or "buildslave" branch in Git, which would be basically Git "master" preview with forced update (history rewrite) option. Normal people should never use this branch, as the history would get rewritten whenever a patch would have to be rolled back. This would help ensure that Git "master" is always in a good shape. That said, doing 1) properly should help mitigate the risk of Git "master" breaking often. The less trivial issues will not be found on a single developer machine anyways. > > > Grumbling aside, our feature page for 2.4 sees us in reasonably good > shape - all the major work has been done, Samuli has done some amazing > work on automated windows testing, and all the test reports we've received > so far have been "yeah, it works". > > So, what is missing for 2.4 (please update the page as you go)? > This is one that I have to fix, unless xkjyeah responds soonish: <https://github.com/xkjyeah/openvpnserv2/issues/10> I can also provide a documentation patch for Trac 757. I added both of these tasks here: <https://community.openvpn.net/openvpn/wiki/StatusOfOpenvpn24> > I see TLS record splitting, which I have no idea how invasive this is > going to be, and how much time is needed to make that happen (and to > test it). A number of trac tickets for specific corner cases (like, > FreeBSD 11 with topology subnet). > > > I still think the timeline "end of 2016" should be doable - there's > some reasoning to meet that: it will make the next Debian release. If Debian 9 is frozen by the end of the year, then that is a good goal. -- 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
