From owner-freebsd-hackers@freebsd.org Tue Jul 9 23:35:02 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7EF8F15E87D5 for ; Tue, 9 Jul 2019 23:35:02 +0000 (UTC) (envelope-from john@kozubik.com) Received: from kozubik.com (kozubik.com [216.218.240.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7A4608C3EA for ; Tue, 9 Jul 2019 23:35:01 +0000 (UTC) (envelope-from john@kozubik.com) Received: from kozubik.com (localhost [127.0.0.1]) by kozubik.com (8.14.3/8.14.3) with ESMTP id x69NTnlM062019 for ; Tue, 9 Jul 2019 16:29:49 -0700 (PDT) (envelope-from john@kozubik.com) Received: from localhost (john@localhost) by kozubik.com (8.14.3/8.14.3/Submit) with ESMTP id x69NTitS062016 for ; Tue, 9 Jul 2019 16:29:44 -0700 (PDT) (envelope-from john@kozubik.com) Date: Tue, 9 Jul 2019 16:29:44 -0700 (PDT) From: John Kozubik To: freebsd-hackers@freebsd.org Subject: How many "production" releases will FreeBSD have when the ZoL merge comes in ? Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Rspamd-Queue-Id: 7A4608C3EA X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of john@kozubik.com designates 216.218.240.130 as permitted sender) smtp.mailfrom=john@kozubik.com X-Spamd-Result: default: False [-2.68 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.91)[-0.911,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[130.240.218.216.list.dnswl.org : 127.0.6.2]; MX_GOOD(-0.01)[kozubik.com]; DMARC_NA(0.00)[kozubik.com]; NEURAL_HAM_SHORT(-0.70)[-0.704,0]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:6939, ipnet:216.218.128.0/17, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.55)[ipnet: 216.218.128.0/17(0.40), asn: 6939(-3.12), country: US(-0.06)] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jul 2019 23:35:02 -0000 Friends, I am confused as to how the ZFS On Linux merge will be available before 2022. The current supported release lifecycle page states: "11.4-RELEASE + 3 months (or September 30, 2021)" ... and I have heard very pessimistic responses about the ZoL merge going into the 12 branch. So I *think* that one of the following must be true: - We will, at some point, have *three* production branches with -RELEASE distributions: 11, 12 and 13. - ZoL will actually come into the 12 branch, despite recent pessimism. - Neither of the above: ZoL comes in the 13 branch, which will not overlap with the 11 branch, which means (basically) 2022 as the earliest production (-RELEASE) version of FreeBSD with ZoL. Some background ... We at rsync.net, which runs exclusively on FreeBSD, are *dying* to get native encryption and raw send. As you can imagine, we can only run -RELEASE versions of FreeBSD. We really want to give Linux users the ability to 'zfs send' to their rsync.net accounts like FreeBSD users do, but 13.1-RELEASE[1] is a *long* way off - perhaps over three years from now. Three simultaneous "production" releases seems silly. So that leaves ZoL coming in the 12 branch as the only outcome that isn't terrible news. I wonder if there is any of the above that I am mistaken about, or some news I have missed ? Thanks, John Kozubik [1] In practice, we also don't run x.0 releases in production which sounds bigoted and superstitious but I can point to 5.0-RELEASE and you need no further explanation.