From owner-freebsd-stable@freebsd.org Tue Sep 19 08:15:34 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 CE53EE03C41 for ; Tue, 19 Sep 2017 08:15:34 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (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 9405470007 for ; Tue, 19 Sep 2017 08:15:34 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1duDgq-000Fbl-O4; Tue, 19 Sep 2017 10:15:32 +0200 Date: Tue, 19 Sep 2017 10:15:32 +0200 From: Kurt Jaeger To: Aristedes Maniatis Cc: freebsd-stable Subject: Re: ABI changes within stable branch Message-ID: <20170919081532.GB2170@home.opsec.eu> References: <1b07bf49-508a-c6b4-e805-df7d43230f81@ish.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1b07bf49-508a-c6b4-e805-df7d43230f81@ish.com.au> 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:15:34 -0000 Hi! > 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. I think it was the other way around: All ports build on the .0 of a RELEASE work on all later .x of that RELEASE. Which makes it a bit difficult, if a .0 is no longer supported/patched by the secteam. A pointer to the official policy would be nice 8-} -- pi@opsec.eu +49 171 3101372 3 years to go !