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

Section Navigation

FreeBSD 10.1 Release Process


This is the release schedule for FreeBSD 10.1. 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


Action Expected Actual Description
Initial release schedule announcement - 10July2014 Release Engineers send announcement email to developers with a rough schedule.
Release schedule reminder 10August2014 10August2014 Release Engineers send reminder announcement e-mail to developers with updated schedule.
Code slush begins 22August2014 22August2014 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 5September2014 5September2014 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 12September2014 12September2014 First beta test snapshot.
BETA2 builds begin 19September2014 19September2014 Second beta test snapshot.
BETA3 builds begin 26September2014 26September2014 Third beta test snapshot.
releng/10.1 branch 3October2014 3October2014 Subversion branch created; future release engineering proceeds on this branch.
RC1 builds begin 3October2014 3October2014 First release candidate.
RC2 builds begin 10October2014 10October2014 Second release candidate.
RC3 builds begin 17October2014 21October2014 Third release candidate.
RC4 builds begin* 29October2014 30October2014 Fourth release candidate.
RELEASE builds begin 24October2014
11November2014 10.1-RELEASE builds begin.
RELEASE announcement 29October2014
14November2014 10.1-RELEASE press release.
Turn over to the secteam - 26November2014 releng/10.1 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

"*" indicates late additions to the schedule.

Status / TODO

FreeBSD Release Engineering TODO Page

Additional Information