FreeBSD 13.1 Release Process
Introduction
This is the release schedule for FreeBSD 13.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 are no longer being accepted.
Schedule
Action | Expected | Actual | Description |
---|---|---|---|
Initial release schedule announcement |
- |
1 February 2022 |
Release Engineers send announcement email to developers with a rough schedule. |
Release schedule reminder |
12 February 2022 |
12 February 2022 |
Release Engineers send reminder announcement e-mail to developers with updated schedule. |
Code slush begins |
24 February 2022 |
24 February 2022 |
Release Engineers announce that all further commits to the stable/13 branch will not require explicit approval, however new features should be avoided. |
releng/13.1 branch |
10 March 2022 |
10 March 2022 |
releng/13.1 branch created; future release engineering proceeds on this branch. |
BETA1 builds begin |
10 March 2022 |
10 March 2022 |
First beta test snapshot. |
BETA2 builds begin |
17 March 2022 |
17 March 2022 |
Second beta test snapshot. |
BETA3 builds begin |
24 March 2022 |
24 March 2022 |
Third beta test snapshot. |
RC1 builds begin |
31 March 2022 |
31 March 2022 |
First release candidate. |
RC2 builds begin |
7 April 2022 |
7 April 2022 |
Second release candidate. |
RC3 builds begin |
14 April 2022 |
14 April 2022 |
Third release candidate. |
RC4 builds begin |
21 April 2022 |
21 April 2022 |
Fourth release candidate. |
RC5 builds begin |
28 April 2022 |
28 April 2022 |
Fifth release candidate. |
RC6 builds begin |
5 May 2022 |
5 May 2022 |
Sixth release candidate. |
RELEASE builds begin |
12 May 2022 |
12 May 2022 |
13.1-RELEASE builds begin. |
RELEASE announcement |
16 May 2022 |
16 May 2022 |
13.1-RELEASE press release. |
Turn over to the secteam |
- |
3 June 2022 |
releng/13.1 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
"*" indicates "as-needed" items.
Additional Information
Last modified on: February 6, 2024 by Paul Ivanov