From owner-freebsd-security@freebsd.org Sun Dec 10 05:55:32 2017 Return-Path: Delivered-To: freebsd-security@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 9510AE832F9 for ; Sun, 10 Dec 2017 05:55:32 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (wollman-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::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 5A53C64D8B for ; Sun, 10 Dec 2017 05:55:32 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.15.2/8.15.2) with ESMTP id vBA5tTht031823; Sun, 10 Dec 2017 00:55:29 -0500 (EST) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.15.2/8.14.4/Submit) id vBA5tTnh031822; Sun, 10 Dec 2017 00:55:29 -0500 (EST) (envelope-from wollman) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <23084.52304.918811.943377@hergotha.csail.mit.edu> Date: Sun, 10 Dec 2017 00:55:28 -0500 From: Garrett Wollman To: Franco Fichtner Cc: freebsd-security Subject: Re: [FreeBSD-Announce] FreeBSD 11.0 end-of-life In-Reply-To: References: <20171208192538.C5C4D1C234@freefall.freebsd.org> X-Mailer: VM 8.2.0b under 25.3.1 (amd64-portbld-freebsd10.3) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (hergotha.csail.mit.edu [127.0.0.1]); Sun, 10 Dec 2017 00:55:29 -0500 (EST) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED, HEADER_FROM_DIFFERENT_DOMAINS autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hergotha.csail.mit.edu X-Mailman-Approved-At: Sun, 10 Dec 2017 12:20:41 +0000 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 05:55:32 -0000 < said: > Hi, >> On 8. Dec 2017, at 8:25 PM, FreeBSD Security Officer wrote: >> >> +--------------------------------------------------+-----------------------+ >> |releng/11.1|11.1-RELEASE|n/a |July 26, 2017 |11.2-RELEASE + 3 months| >> +--------------------------------------------------+-----------------------+ > Is there *any* indication when X + 3 is going to be? Because as a downstream > vendor X + 3 months usually translates to X, because there is no time to prepare > for any of this, especially when swift adoption is enforced by upstream, e.g. > by deprecated packages, quarterly branch and locking users out of the ports tree. Yeah, that's been one of my concerns all along with this new deprecation schedule. It takes me about a month to qualify a new release, and we have only two windows a year when I can actually deploy it (after testing) -- from 12/26 to 12/30, and from the Monday after the first Saturday in June until the Friday before the first Monday in September.[1] Release schedules in recent years have been pretty pessimal for me as it is. I'll be rolling out 11.1 later this month, but if 11.2 were to happen in March I'd be SOL before I could even think about upgrading. -GAWollman [1] And not coincidentally, these are the times when everybody, myself included, wants to go on vacation.