Date: Tue, 23 Aug 2016 04:01:27 +0000 From: Glen Barber <gjb@FreeBSD.org> To: Karl Denninger <karl@denninger.net> Cc: freebsd-stable@freebsd.org Subject: Re: Delay with 11.0-RC2 builds Message-ID: <20160823040127.GG765@FreeBSD.org> In-Reply-To: <50aeed81-fdb2-83a4-10c8-d4e50b0d5684@denninger.net> References: <20160818233024.GZ765@FreeBSD.org> <20160823034319.GG54084@FreeBSD.org> <50aeed81-fdb2-83a4-10c8-d4e50b0d5684@denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--0YvPcIOsea23f0hb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 22, 2016 at 10:53:06PM -0500, Karl Denninger wrote: > On 8/22/2016 22:43, Glen Barber wrote: > > On Thu, Aug 18, 2016 at 11:30:24PM +0000, Glen Barber wrote: > >> Two issues have been brought to our attention, and as a result, 11.0-R= C2 > >> builds will be delayed a day or two while these are investigated. > >> > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211872 > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211926 > >> > >> An update will be sent if the delay is longer than anticipated. > >> > > Just an update, the 11.0-RC2 will be delayed at least two days. One of > > the issues mentioned in the above PR URLs does not affect releng/11.0, > > and is a non-issue, but we are awaiting one more change to the stable/11 > > and releng/11.0 branches that we hope will be the final major changes to > > 11.0. > > > > If this is the case, we may be able to eliminate 11.0-RC3 entirely, and > > still release on time (or, on time as the current schedule suggests). > > > > However, as you know, FreeBSD releases prioritize quality over schedule, > > so we may still need to adjust the schedule appropriately. > > > > So, help with testing 11.0-RC1 (or the latest releng/11.0 from svn) is > > greatly appreciated. > > > > Glen > > On behalf of: re@ > > > Has any decision been made on this? >=20 > It is not local to me (others have reported problems with combination > devices) and rolling back the change in question eliminates the > problem. It remains un-triaged as of this point. >=20 > Note that this impacts a system that is booting and needs manual > intervention, which is not a good place to a have a problem.... >=20 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211884 >=20 Well, it's an EN candidate if we cannot get it fixed before the release. But, I've put it on our radar, which it was not on mine previously... Glen --0YvPcIOsea23f0hb Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXu8qXAAoJEAMUWKVHj+KTdrAP/09BOkbbf1GgAb90cVHsmwbn g/9RxTsGhNxiuDKg8xLDAcscwAs3XmvYaf+Dywk8fjvMJvdVaZGlVMP9dOdvC5n1 fUUqh9erTOLo0YJzGBpNZZnIfpLrAsUJb6W7Oqei6gk50ZHxMmKVqTmwZlmQb84p qmQ2eM0/NkwnMA0Pkh/lHLhP7zWH64cDSWxk+KQspfF6I9YVW8Iwo68QiUQGoQTl uJwAZGbo9mrq11gUC4WcNDqxpkfXu8POwii1sHym8671AlNggmQmKwmKAIdBL0J0 L9r6x/ggihd6tAD2gsTMKRaxahbyeXaLiwMo7zvHJEgeii7nHVWJ4V6S6JE/OeP4 G2h6txDzNxKkAq88KMAnO5P1iQz2K+pw6+JE3LKXRNLEoOGEXfUdEsqHwIE/UsjF 1vEamYI/brdFnV/HDwbA49Q7Pk3XRSspQ8A++7Tm/wCdi0bUXzFBoTAvdsoaKCVA dMi+L2OjzypYMx5L4WwxWVkNYJRr6fX8QZV+4u3rRClDr2nr4lhoM03NG9GpJLr1 jeKguK+DP6/nuowxG4LnO0lq1fQkdpG3RqEuLX5nrX2o0TB9bninwG3EXYUKMhNH CHK2rH2zdzG/MN/kk7fZMNbBPREm3CiC+cJOpTfo9yz9Kkfi/x9sg8uRsm8IWuTd pMf2ntzauz0AyET88z7o =IuBc -----END PGP SIGNATURE----- --0YvPcIOsea23f0hb--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160823040127.GG765>