This is the index page for &os; &local.rel;. For more - information about the release engineering process, please see the - Release Engineering section - of the web site.
+This is the index page for &os; &local.rel;. For more + information about the release engineering process, please see + the Release Engineering + section of the web site.
-More detailed information, such as release notes and hardware - notes can be found at these pages:
+More detailed information, such as release notes and hardware + notes can be found at these pages:
- &os; &local.rel;-RELEASE signed checksum filesAlthough the &os; &local.rel; schedule has not yet been - written, the release cycle is currently anticipated to begin - around February 2019. This page will be updated accordingly if - this anticipated timeframe should change.
+Although the &os; &local.rel; schedule has not yet been + written, the release cycle is currently anticipated to begin + around February 2019. This page will be updated accordingly if + this anticipated timeframe should change.
- General discussions about the pending release and known issues should be - sent to the public - freebsd-current mailing list. - MFC - requests should be sent to - re@FreeBSD.org. + General discussions about the pending release and known issues + should be sent to the public freebsd-current + mailing list. MFC + requests should be sent to re@FreeBSD.org. - &beta.local.where; - &beta2.local.where; + &beta.local.where; + &beta2.local.where; -During the &local.branch.head; freeze, the Release Engineering - Team may create ALPHA snapshots to publish for testing purposes. - As the frequency and total number of the ALPHA snapshots will - depend on the length of time the &local.branch.head; branch is - frozen, no official schedule is provided.
+During the &local.branch.head; freeze, the Release Engineering + Team may create ALPHA snapshots to publish for testing purposes. + As the frequency and total number of the ALPHA snapshots will + depend on the length of time the &local.branch.head; branch is + frozen, no official schedule is provided.
-Announcements regarding the availability of the - ALPHA snapshots will be sent to the freebsd-current - and freebsd-snapshots - mailing lists.
+Announcements regarding the availability of the ALPHA snapshots + will be sent to the freebsd-current + and freebsd-snapshots + mailing lists.
-| Action | -Expected | -Actual | -Description | -
| Action | +Expected | +Actual | +Description | +
| Initial release schedule announcement | -- | -- | -Release Engineers send announcement email to developers with - a rough schedule. | -
| Initial release schedule announcement | +- | +- | +Release Engineers send announcement email to developers + with a rough schedule. | +
| Release schedule reminder | -- | -- | -Release Engineers send reminder announcement e-mail to - developers with updated schedule. | -
| Release schedule reminder | +- | +- | +Release Engineers send reminder announcement e-mail to + developers with updated schedule. | +
| Code slush begins | -- | -- | -Release Engineers announce that all further commits to the - &local.branch.head; branch will not require explicit - approval, however new features should be avoided. | -
| Code slush begins | +- | +- | +Release Engineers announce that all further commits to the + &local.branch.head; branch will not require explicit + approval, however new features should be avoided. | +
| Code freeze begins | -- | -- | -Release Engineers announce that all further commits to the - &local.branch.head; branch will require explicit approval. - Certain blanket approvals will be granted for narrow areas of - development, documentation improvements, etc. | -
| Code freeze begins | +- | +- | +Release Engineers announce that all further commits to the + &local.branch.head; branch will require explicit approval. + Certain blanket approvals will be granted for narrow areas + of development, documentation improvements, etc. | +
| KBI freeze begins | -- | -- | -Release Engineers announce that all further commits to the - &local.branch.head; branch will require explicit approval. - Additionally, there can be no changes to the KBI until - &local.branch.head; is branched to &local.branch.stable;. | -
| KBI freeze begins | +- | +- | +Release Engineers announce that all further commits to the + &local.branch.head; branch will require explicit approval. + Additionally, there can be no changes to the KBI until + &local.branch.head; is branched to + &local.branch.stable;. | +
| &local.branch.stable; branch | -- | -- | -Subversion branch created; release engineering continues - on this branch. | -
| &local.branch.stable; branch | +- | +- | +Subversion branch created; release engineering continues + on this branch. | +
| BETA1 builds begin | -- | -- | -First beta test snapshot. | -
| BETA1 builds begin | +- | +- | +First beta test snapshot. | +
| &local.branch.head; thaw | -- | -- | -The code freeze on the &local.branch.head; branch - is lifted. | -
| &local.branch.head; thaw | +- | +- | +The code freeze on the &local.branch.head; branch + is lifted. | +
| BETA2 builds begin | -- | -- | -Second beta test snapshot. | -
| BETA2 builds begin | +- | +- | +Second beta test snapshot. | +
| BETA3 builds begin | -- | -- | -Third beta test snapshot. | -
| BETA3 builds begin | +- | +- | +Third beta test snapshot. | +
| &local.branch.releng; branch | -- | -- | -Subversion branch created; future release engineering - proceeds on this branch. | -
| &local.branch.releng; branch | +- | +- | +Subversion branch created; future release engineering + proceeds on this branch. | +
| RC1 builds begin | -- | -- | -First release candidate. | -
| RC1 builds begin | +- | +- | +First release candidate. | +
| &local.branch.stable; thaw | -- | -- | -The code freeze on the &local.branch.stable; branch - is lifted. | -
| &local.branch.stable; thaw | +- | +- | +The code freeze on the &local.branch.stable; branch + is lifted. | +
| RC2 builds begin | -- | -- | -Second release candidate. | -
| RC2 builds begin | +- | +- | +Second release candidate. | +
| RC3 builds begin | -- | -- | -Third release candidate. | -
| RC3 builds begin | +- | +- | +Third release candidate. | +
| RELEASE builds begin | -- | -- | -&local.rel;-RELEASE builds begin. | -
| RELEASE builds begin | +- | +- | +&local.rel;-RELEASE builds begin. | +
| RELEASE announcement | -- | -- | -&local.rel;-RELEASE press release. | -
| RELEASE announcement | +- | +- | +&local.rel;-RELEASE press release. | +
| Turn over to the secteam | -- | -- | -&local.branch.releng; branch is handed over to the - &os; Security Officer Team in one or two weeks after the - announcement. | -
"*" indicates "as-needed" items.
+"*" indicates "as-needed" items.
-