Skip site navigation (1) Skip section navigation (2)

Section Navigation

FreeBSD 10.3 Release Process


This is the release schedule for FreeBSD10.3. 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 are no longer being accepted at this time.


Action Expected Actual Description
Initial release schedule announcement - 6October2015 Release Engineers send announcement email to developers with a rough schedule.
Release schedule reminder 15November2015 3December2015 Release Engineers send reminder announcement e-mail to developers with updated schedule.
Code slush begins 15January2016 15January2016 Release Engineers announce that all further commits to the stable/10 branch will not require explicit approval, however new features should be avoided.
Code freeze begins 29January2016 29January2016 Release Engineers announce that all further commits to the stable/10 branch will require explicit approval. Certain blanket approvals will be granted for narrow areas of development, documentation improvements, etc.
BETA1 builds begin 5February2016 5February2016 First beta test snapshot.
BETA2 builds begin 12February2016 12February2016 Second beta test snapshot.
BETA3 builds begin* 26February2016 26February2016 Third beta test snapshot.
releng/10.3 branch 4March2016 4March2016 Subversion branch created; future release engineering proceeds on this branch.
RC1 builds begin 4March2016 4March2016 First release candidate.
stable/10thaw 6March2016 6March2016 The code freeze on the stable/10 branch is lifted.
RC2 builds begin 11March2016 11March2016 Second release candidate.
RC3 builds begin* 18March2016 18March2016 Third release candidate.
RELEASE builds begin 25March2016 25March2016 10.3-RELEASE builds begin.
RELEASE announcement 29March2016 4April2016 10.3-RELEASE press release.
Turn over to the secteam - 27April2016 releng/10.3 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

"*" indicates "as-needed" items.

Status / TODO

FreeBSD Release Engineering TODO Page

Additional Information