|
Lines 8-42
sidenav: download
Link Here
|
| 8 |
:localBranchStable: stable/14 |
8 |
:localBranchStable: stable/14 |
| 9 |
:localBranchReleng: releng/14.0 |
9 |
:localBranchReleng: releng/14.0 |
| 10 |
|
10 |
|
|
|
11 |
include::shared/en/mailing-lists.adoc[] |
| 11 |
include::shared/en/urls.adoc[] |
12 |
include::shared/en/urls.adoc[] |
| 12 |
|
13 |
|
| 13 |
= FreeBSD {localRel} Release Process |
14 |
= FreeBSD {localRel} Release Process |
| 14 |
|
15 |
|
| 15 |
== Introduction |
16 |
This is the release schedule for FreeBSD {localRel}. |
| 16 |
|
17 |
|
| 17 |
This is the release schedule for FreeBSD {localRel}. For more information about the release engineering process, please see the link:../../../releng/[Release Engineering] section of the web site. |
18 |
//// |
|
|
19 |
During the {localBranchHead} freeze, the Release Engineering Team may create and publish ALPHA snapshots for testing purposes. |
| 20 |
As the frequency and number of ALPHA snapshots will depend on the length of time the {localBranchHead} branch is frozen, no official schedule is provided. |
| 18 |
|
21 |
|
| 19 |
General discussions about the pending release and known issues should be sent to the public mailto:FreeBSD-current@FreeBSD.org[freebsd-current] mailing list. |
22 |
ALPHA snapshot announcements will be sent to {freebsd-current-url}[freebsd-current] and {freebsd-snapshots-url}[freebsd-snapshots]. |
| 20 |
|
23 |
|
| 21 |
// link:{handbook}#mfc-glossary[MFC] requests are no longer being accepted for {localBranchReleng}. |
24 |
//// |
|
|
25 |
BETA and RC announcements will be sent to {freebsd-current-url}[freebsd-current] and {freebsd-stable-url}[freebsd-stable]. |
| 26 |
|
| 27 |
For general discussion of the pending release, and known issues, please use the {freebsd-current}. |
| 28 |
|
| 29 |
//link:{handbook}#mfc-glossary[MFC] requests are no longer being accepted for {localBranchReleng}. |
| 22 |
|
30 |
|
| 23 |
//link:{handbook}#mfc-glossary[MFC] requests should be sent to link:mailto:re@FreeBSD.org[re@FreeBSD.org] following the link:https://wiki.freebsd.org/Releng/ChangeRequestGuidelines[Change Request Guidelines]. |
31 |
//link:{handbook}#mfc-glossary[MFC] requests should be sent to link:mailto:re@FreeBSD.org[re@FreeBSD.org] following the link:https://wiki.freebsd.org/Releng/ChangeRequestGuidelines[Change Request Guidelines]. |
| 24 |
|
32 |
|
|
|
33 |
For more information about the process, see link:../../../releng/[Release Engineering]. |
| 34 |
|
| 25 |
== Schedule |
35 |
== Schedule |
| 26 |
|
36 |
|
| 27 |
During the {localBranchHead} 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 {localBranchHead} branch is frozen, no official schedule is provided. |
|
|
| 28 |
|
| 29 |
Announcements regarding the availability of the ALPHA snapshots will be sent to the mailto:freebsd-current@FreeBSD.org[freebsd-current] and mailto:freebsd-snapshots@FreeBSD.org[freebsd-snapshots] mailing lists. |
| 30 |
|
| 31 |
[.tblbasic] |
37 |
[.tblbasic] |
| 32 |
[cols=",,,",options="header",] |
38 |
[cols=",,,",options="header",] |
| 33 |
|=== |
39 |
|=== |
| 34 |
|Action |Expected |Actual |Description |
40 |
|Action |Expected |Actual |Description |
| 35 |
|Initial release schedule announcement |- |26 June 2023 |Release Engineers send announcement email to developers with a rough schedule. |
41 |
|Initial release schedule announcement |- |26 June 2023 |Release Engineers send announcement email to developers with a rough schedule. |
| 36 |
|Release schedule reminder |21 July 2023 |20 July 2023 |Release Engineers send reminder announcement e-mail to developers with updated schedule. |
42 |
|Release schedule reminder |21 July 2023 |20 July 2023 |Release Engineers send reminder announcement e-mail to developers with updated schedule. |
| 37 |
|Code slush begins / KBI freeze |4 August 2023 |3 August 2023 |Release Engineers announce that all further commits to the {localBranchHead} branch will not require explicit approval, however new features should be avoided. Additionally, there can be no changes to the KBI until {localBranchHead} is branched to {localBranchStable}. |
43 |
|Code slush begins / KBI freeze |4 August 2023 |3 August 2023 |Release Engineers announce that all further commits to the {localBranchHead} branch will not require explicit approval, however new features should be avoided. |
|
|
44 |
Additionally, there can be no changes to the KBI until {localBranchHead} is branched to {localBranchStable}. |
| 38 |
|{localBranchStable} branch |25 August 2023 |24 August 2023 |{localBranchStable} branch created; release engineering continues on this branch. |
45 |
|{localBranchStable} branch |25 August 2023 |24 August 2023 |{localBranchStable} branch created; release engineering continues on this branch. |
| 39 |
|{localBranchReleng} branch |8 September 2023 |8 September 2023 |{localBranchReleng} branch created; future release engineering proceeds on this branch. Commits to this branch require explicit approval from the Release Engineers. |
46 |
|{localBranchReleng} branch |8 September 2023 |8 September 2023 |{localBranchReleng} branch created; future release engineering proceeds on this branch. |
|
|
47 |
Commits to this branch require explicit approval from the Release Engineers. |
| 40 |
|BETA1 builds begin |8 September 2023 |8 September 2023 |First beta test snapshot. |
48 |
|BETA1 builds begin |8 September 2023 |8 September 2023 |First beta test snapshot. |
| 41 |
|BETA2 builds begin |15 September 2023 |15 September 2023 |Second beta test snapshot. |
49 |
|BETA2 builds begin |15 September 2023 |15 September 2023 |Second beta test snapshot. |
| 42 |
|BETA3 builds begin |22 September 2023 |22 September 2023 |Third beta test snapshot. |
50 |
|BETA3 builds begin |22 September 2023 |22 September 2023 |Third beta test snapshot. |
|
Lines 45-51
Announcements regarding the availability of the ALPHA snapshots will be sent to
Link Here
|
| 45 |
|RC3 builds begin* |13 October 2023 |- |Third release candidate. |
53 |
|RC3 builds begin* |13 October 2023 |- |Third release candidate. |
| 46 |
|RELEASE builds begin |20 October 2023 |- |{localRel}-RELEASE builds begin. |
54 |
|RELEASE builds begin |20 October 2023 |- |{localRel}-RELEASE builds begin. |
| 47 |
|RELEASE announcement |23 October 2023 |- |{localRel}-RELEASE press release. |
55 |
|RELEASE announcement |23 October 2023 |- |{localRel}-RELEASE press release. |
| 48 |
|Turn over to the secteam |- |- |{localBranchReleng} branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
56 |
|Turn over to the secteam |- |- |{localBranchReleng} branch is handed over to the FreeBSD Security Officer Team one or two weeks after the announcement. |
| 49 |
|=== |
57 |
|=== |
| 50 |
|
58 |
|
| 51 |
"*" indicates "as-needed" items. |
59 |
"*" indicates "as-needed" items. |
|
Lines 54-60
Announcements regarding the availability of the ALPHA snapshots will be sent to
Link Here
|
| 54 |
== Status / TODO |
62 |
== Status / TODO |
| 55 |
link:todo/[FreeBSD Release Engineering TODO Page] |
63 |
link:todo/[FreeBSD Release Engineering TODO Page] |
| 56 |
//// |
64 |
//// |
| 57 |
|
|
|
| 58 |
== Additional Information |
| 59 |
|
| 60 |
* link:../../../releng/[FreeBSD Release Engineering website] |
| 61 |
- |