From owner-freebsd-stable@freebsd.org Tue Sep 19 08:09:39 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BE9AFE0376C for ; Tue, 19 Sep 2017 08:09:39 +0000 (UTC) (envelope-from prvs=0435da476c=ari@ish.com.au) Received: from fish.ish.com.au (ip-2.ish.com.au [203.29.62.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 898E06FBBF for ; Tue, 19 Sep 2017 08:09:38 +0000 (UTC) (envelope-from prvs=0435da476c=ari@ish.com.au) Received: from ip-170.ish.com.au ([203.29.62.170]:56368) by fish.ish.com.au with esmtpsa (TLSv1.2:AES128-SHA:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1duDax-0006nh-26 for freebsd-stable@freebsd.org; Tue, 19 Sep 2017 18:09:28 +1000 X-CTCH-RefID: str=0001.0A150202.59C0D0B7.0104:SCFSTAT42589845, ss=1, re=-4.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 To: freebsd-stable From: Aristedes Maniatis Subject: ABI changes within stable branch Message-ID: <1b07bf49-508a-c6b4-e805-df7d43230f81@ish.com.au> Date: Tue, 19 Sep 2017 18:09:25 +1000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:56.0) Gecko/20100101 Thunderbird/56.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2017 08:09:39 -0000 Now that we are on a faster upgrade policy for minor branches, it is expected that we'll upgrade from 11.0 to 11.1 to 11.2 much faster than in the old days. I can cope with that, but it appears that functional changes are also being made within the stable branch as seen here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221672 A new fdatasync() method is available in 11.1 but not in 11.0 which means that I now need to maintain separate ports trees for each minor update. I've never done this before, assuming (correctly for me until now) that all ports build on the latest minor release within the stable branch would work on older releases until I was ready to upgrade them. Is this instance a mistake or am I misunderstanding the new policy? If I need to treat each release within the stable branch as a whole new platform for ports, that means a bunch of extra testing and maintenance work for me. Cheers Ari -- --------------------------> Aristedes Maniatis CEO, ish https://www.ish.com.au GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A