From owner-freebsd-stable@freebsd.org Wed Mar 28 16:42:04 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96364F6BB7D; Wed, 28 Mar 2018 16:42:04 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 464CB75D0E; Wed, 28 Mar 2018 16:42:04 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id DF853C063; Wed, 28 Mar 2018 16:42:03 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Wed, 28 Mar 2018 16:42:02 +0000 From: Glen Barber To: freebsd-stable@freebsd.org Cc: FreeBSD Release Engineering Team Subject: HEADS-UP: 11.2-RELEASE cycle starting in one month Message-ID: <20180328164202.GA59100@FreeBSD.org> Reply-To: FreeBSD Release Engineering Team MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Mar 2018 16:42:04 -0000 --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline [Several vendor contacts in BCC.] For those that did not notice the website update adding the 11.2-RELEASE cycle schedule, I apologize for sending this to public lists this late. I thought I had done this, but apparently not. The 11.2-RELEASE release cycle will begin April 20, 2018. The schedule for the release cycle is: stable/11 slush: April 20, 2018 stable/11 freeze: May 4, 2018 BETA1 build starts: May 11, 2018 doc/ tree slush: May 12, 2018 BETA2 build starts: May 18, 2018 BETA3 build starts: May 25, 2018 [*] doc/ tree tag: May 26, 2018 releng/11.2 branch: June 1, 2018 RC1 build starts: June 1, 2018 stable/11 thaw: June 3, 2018 RC2 build starts: June 8, 2018 RC3 build starts: June 15, 2018 [*] RELEASE build starts: June 22, 2018 RELEASE announcement: June 27, 2018 11.1-RELEASE EoL: September 30, 2018 Branch EoL: September 30, 2021 [*] - If needed The schedule is also available on the Project website at: https://www.freebsd.org/releases/11.2R/schedule.html As a reminder, the code "slush" is not a hard freeze on the tree and does not require formal approval from re@, however we ask that you refrain from adding new features, and focus on fixing existing issues. The code "freeze" is the point at which all commits to stable/11 will require explicit approval from re@. If you are aware of any problems in stable/11, please let re@ know as soon as possible. Additionally, if vendors have driver updates that are planned to be included in 11.2-RELEASE, please ensure the drivers are updated in head (preferably as soon as possible, to catch any issues), and merged to stable/11 following the minimum 3-day MFC timeframe. Thank you. Glen On behalf of: re@ --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlq7xdoACgkQAxRYpUeP 4pPG1Q/+I1WO+9LA92DzYFVNygSgKwnHbzs6/LWe78JQGfV5iRIeaJbpZVKQcqNI HEN4AM9wYavDzOmafNb6CSfBwPV9IYcdSfBSyk7/BI3Wo3jeTdVXkOZzEtn4Kix/ KT7sLJ354HTxXVmgdMVVCI8LxTwD9jYpem5Xq1s4gTKmz/Z9Km8/47MSUBLDTRi2 LFFUYp1xbekweTWXXpVjXXrlB0UkP3zvDu8QLHNCbQkV+UN0Hkrv5kF7zKzVMt+d vscrRl2H1xr88s9BkYpRPpfauWbrIJm15WrGm32Q8r3EK153hgn7BzkKO8gDIExT eRjgea+OMC7BFx49+oEJJzbN8EwJ8T8upZs5rDJaEzFqm+LJELthdUrig7flMK8R ZEUKqAGB3l3JPvUYKx35rcbls+OcJU5LnBWsj/oJSPsltGnkALbRwYHzZr99yF2U vZMgyKfWU05KVCotkxvszxS6YfqmWQwDZaJnJe5W6qVWUzZsyE+zJ9DrT0fUbHVR VRtILMwRWMELT0AFtS9BvByaWSNHNc15TR0SW2vM4Nt/jk5+kabmFB3Fgqz0pMAs a0h2G8Vnqg7K8RMmiHrZeUp1kkcW3NTgFYvPqr8j+N3zgr9kC3odAnYByZUKYQuM eg7JYkUmFGQR1jxLrY3JQ9AoRTwtIkO+O7uPWjzKbs4Efx1N7Ik= =qCZ0 -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx--