From owner-freebsd-security@freebsd.org  Sat Dec  9 07:05:56 2017
Return-Path: <owner-freebsd-security@freebsd.org>
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 2F874E813B6
 for <freebsd-security@mailman.ysv.freebsd.org>;
 Sat,  9 Dec 2017 07:05:56 +0000 (UTC)
 (envelope-from franco@lastsummer.de)
Received: from host64.shmhost.net (host64.shmhost.net [213.239.241.64])
 (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 ECC1E7A219
 for <freebsd-security@freebsd.org>; Sat,  9 Dec 2017 07:05:55 +0000 (UTC)
 (envelope-from franco@lastsummer.de)
Received: from francos-mbp.homeoffice.local
 (dslb-178-012-107-202.178.012.pools.vodafone-ip.de [178.12.107.202])
 by host64.shmhost.net (Postfix) with ESMTPSA id 79E58160859
 for <freebsd-security@freebsd.org>; Sat,  9 Dec 2017 08:05:52 +0100 (CET)
From: Franco Fichtner <franco@lastsummer.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [FreeBSD-Announce] FreeBSD 11.0 end-of-life
Date: Sat, 9 Dec 2017 08:05:51 +0100
References: <20171208192538.C5C4D1C234@freefall.freebsd.org>
To: freebsd-security <freebsd-security@freebsd.org>
In-Reply-To: <20171208192538.C5C4D1C234@freefall.freebsd.org>
Message-Id: <C1396C58-89D1-4958-8B6E-D57129ACC475@lastsummer.de>
X-Mailer: Apple Mail (2.3273)
X-Virus-Scanned: clamav-milter 0.99.2 at host64.shmhost.net
X-Virus-Status: Clean
X-Spam-Flag: NO
X-Spam-Score: -1.0
X-Spam-Status: No score=-1.0 tagged_above=10.0 required=10.0
 tests=[ALL_TRUSTED]
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Dec 2017 07:05:56 -0000

Hi,

> On 8. Dec 2017, at 8:25 PM, FreeBSD Security Officer =
<security-officer@freebsd.org> wrote:
>=20
> =
+--------------------------------------------------+----------------------=
-+
> |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.

To that end, https://www.freebsd.org/releng/index.html states:

> Upcoming Release Schedule

> NOTE: Release dates are approximate and may be subject to schedule =
slippage.

> As of 2017-10-03, the next release has not yet been announced.


Thank you,
Franco=