From owner-freebsd-questions@freebsd.org Thu Mar 10 08:59:29 2016 Return-Path: Delivered-To: freebsd-questions@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 86BBDAC7861 for ; Thu, 10 Mar 2016 08:59:29 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from bede.qeng-ho.org (bede.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fileserver.home.qeng-ho.org", Issuer "fileserver.home.qeng-ho.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 247941ECD for ; Thu, 10 Mar 2016 08:59:28 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from arthur.home.qeng-ho.org (arthur.home.qeng-ho.org [172.23.1.2]) by bede.home.qeng-ho.org (8.15.2/8.15.2) with ESMTP id u2A8xINZ035696; Thu, 10 Mar 2016 08:59:19 GMT (envelope-from freebsd@qeng-ho.org) Subject: Re: Upcoming Releases To: Doug Hardie , FreeBSD Questions References: <20160305181742.9c3abe96.freebsd@edvax.de> Cc: Polytropon From: Arthur Chance Message-ID: <56E13766.4040604@qeng-ho.org> Date: Thu, 10 Mar 2016 08:59:18 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 08:59:29 -0000 On 09/03/2016 22:54, Doug Hardie wrote: > >> On 7 March 2016, at 16:23, Doug Hardie wrote: >> >> What I was hoping to find was some form of informal, preliminary >> version of the release notes or announcements for 10.3 and 11. I >> seem to recall some sort of discussion of that back when the >> decision was made to drop bind from the base. I wasn't able to >> find it though. > > I recently saw a comment in one of the maillists that 11.0 was > likely to have the new packetized base feature. That tells me that > 11.0 is most likely to be dicey to work with. I am reminded when > the new pkg system came out and the supporting servers were > compromised. It caused me a lot of issues. I still have one > production server I can't upgrade the ports as its setup for the > temporary solution. I can't recall what I changed and making it > look like the working systems doesn't help. Thus, I will skip 11.0 > and wait for the dust from that to settle. I'll be upgrading to > 10.3 in June. It's always worth remembering the old bit of computing folklore that IBM defined "the lunatic fringe" as those who took the x.0 release of any software. When 11.0 comes out I'll wait a week to see if there are any loud screams and then try it out on my desktop, as boot environments make it easy to roll back. If it tests out OK, then I'll deploy it to my servers. Unlike many other pieces of software, I've rarely had any problems with an x.0 release of FBSD, which says a lot about the release team's competence. Most of the problems I've seen raised come from people not reading the release notes properly, like the "what's happened to bind?" problems with 10.0. -- Moore's Law of Mad Science: Every eighteen months, the minimum IQ necessary to destroy the world drops by one point.