From owner-freebsd-current@freebsd.org Fri Jul 15 00:08:59 2016 Return-Path: Delivered-To: freebsd-current@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 0DE5AB99D65; Fri, 15 Jul 2016 00:08:59 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id F37FD1D5C; Fri, 15 Jul 2016 00:08:58 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 9E9C31662; Fri, 15 Jul 2016 00:08:58 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 15 Jul 2016 00:08:57 +0000 From: Glen Barber To: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Cc: FreeBSD Release Engineering Team Subject: Re: 11.0-BETA2 may be delayed Message-ID: <20160715000857.GT4690@FreeBSD.org> References: <20160713231017.GA95249@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="tbn31orTZdSAVHoc" Content-Disposition: inline In-Reply-To: <20160713231017.GA95249@FreeBSD.org> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2016 00:08:59 -0000 --tbn31orTZdSAVHoc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 13, 2016 at 11:10:17PM +0000, Glen Barber wrote: > As I am sure you have already seen, there is an issue in 11.0-BETA1 that > has caused some headaches for people. >=20 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210884 >=20 > The issue is actively being investigated, and despite the KBI freeze, > the fix may need to break KBI in stable/11, at least as far as I am > aware at the moment. >=20 > That said, 11.0-BETA2 may be delayed, while this is properly resolved. > If KBI is changed between 11.0-BETA1 and 11.0-BETA2, it will be noted in > the announcement. >=20 The latest patch for this issue seems promising so far, but for the sake of being cautious, 11.0-BETA2 is going to be delayed by a few days. The rationale is that we want to see the affected machines survive uptime of at least 48 hours. At this point, we are looking at the fix being committed in just over one day, followed by the normal 3-day MFC timeframe. If this changes, an update will be emailed. Apologies again for the delay with 11.0-BETA2, and thank you for your patience. Glen On behalf of: re@ --tbn31orTZdSAVHoc Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXiCmZAAoJEAMUWKVHj+KTqdoQAJ0kOIrG4o7Je/nR9lCSaEUL 3t496ej9OLPHXoM6h6Ldn8QvfPb37Co4PuCmlwXItyN04Jxb5bfhYFMwiszMqwjL VdLQ9cBgTR4JPuXd2pFBmo/6Vwkr+cPfGg69+ety80S9yyEdmvoNc0HjYrPizfj9 M7DkVJaW4L2vlvmdMz82Z/dD3jsX/ZcXJDL1/XNlK3P+Fb/RnPh6Du9CsRCkTft1 mOQwRZ28kbnXl1+VrfM5Kk1k/2bThJBbbvZItkHCVxI3bNoUlv3+CsrKGgPYiiZw UHKA56JPBjQcbkPICvW8HrdlU/1GlwMDRjxlw0YXL7qhO3PCGefYy5pMt7JQG8fd I2qv5Oc/vBSAJkVmF5kKc3e1jbw3fWDDEsY0IU80aT68M3g9EZ8vA9fDQPUppIwJ //DU0X8ICqbLr47yGeiJom+CmodcecuTmqA8cETqe+drBbDqRtkgO6P/f/28yLGx aLSpXbixhqCvj4q+6PlHyZ31MUEmwjiwAKEydCsK3aUuvHzJPMuYVJWv3x9yVU05 cr+lECOsKt8Y7U3DV6ikGmgmhvnBnvKYigSbhPsl+PCvOKliIk7WsqIAmQkLAF6l 8oMGJPb66xOhINTsVTgDlo5jQSMlnEm1d7MlTsjZ1qRpLHKR0ZH7QoIegu886AP1 zslJ2KTZg0t0QaHricBa =eNmW -----END PGP SIGNATURE----- --tbn31orTZdSAVHoc--