FreeBSD 11.2 Release Process
Introduction
This is the release schedule for FreeBSD�11.2. For more information about the release engineering process, please see the Release Engineering section of the web site.
General discussions about the pending release and known issues should be sent to the public freebsd-stable mailing list. MFC requests should be sent to re@FreeBSD.org.
Schedule
| Action | Expected | Actual | Description |
| Initial release schedule announcement | - | 12�February�2018 | Release Engineers send announcement email to developers with a rough schedule. |
| Release schedule reminder | 16�March�2018 | 16�March�2018 | Release Engineers send reminder announcement e-mail to developers with updated schedule. |
| Code slush begins | 20�April�2018 | - | Release Engineers announce that all further commits to the stable/11 branch will not require explicit approval, however new features should be avoided. |
| Code freeze begins | 4�May�2018 | - | Release Engineers announce that all further commits to the stable/11 branch will require explicit approval. Certain blanket approvals will be granted for narrow areas of development, documentation improvements, etc. |
| BETA1 builds begin | 11�May�2018 | - | First beta test snapshot. |
| BETA2 builds begin | 18�May�2018 | - | Second beta test snapshot. |
| BETA3 builds begin�* | 25�May�2018 | - | Third beta test snapshot. |
| releng/11.2 branch | 1�June�2018 | - | Subversion branch created; future release engineering proceeds on this branch. |
| RC1 builds begin | 1�June�2018 | - | First release candidate. |
| stable/11�thaw | 3�June�2018 | - | The code freeze on the stable/11 branch is lifted. |
| RC2 builds begin | 8�June�2018 | - | Second release candidate. |
| RC3 builds begin�* | 15�June�2018� | - | Third release candidate. |
| RELEASE builds begin | 22�June�2018 | - | 11.2-RELEASE builds begin. |
| RELEASE announcement | 27�June�2018 | - | 11.2-RELEASE press release. |
| Turn over to the secteam | - | - | releng/11.2 branch is handed over to the FreeBSD�Security Officer Team in one or two weeks after the announcement. |
"*" indicates "as-needed" items.