blob: d5922d46c8b8a2dae80acd5d24222cb631640ccf (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
|
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD$">
<!ENTITY local.rel "7.2">
<!ENTITY local.rel.tag "7_2">
<!ENTITY title "FreeBSD &local.rel; Release Process">
<!ENTITY % navinclude.download "INCLUDE">
]>
<html>
&header;
<h1>Introduction</h1>
<p>This is a specific schedule for the release of FreeBSD &local.rel;. For
more general information about the release engineering process,
please see the <a href="&base;/releng/index.html">Release
Engineering</a> section of the web site.</p>
<p>General discussions about the pending release and known issues should be
sent to the public
<a href="mailto:FreeBSD-stable@FreeBSD.org">freebsd-stable</a> mailing list.
<a href="&base;/doc/en_US.ISO8859-1/books/handbook/freebsd-glossary.html#MFC-GLOSSARY">MFC</a>
requests should be sent to
<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>.</p>
<h1>Schedule</h1>
<table class="tblbasic">
<tr class="heading">
<td>Action</td>
<td>Expected</td>
<td>Actual</td>
<td>Description</td>
</tr>
<tr>
<td>Reminder announcement</td>
<td>16 March 2009</td>
<td>17 March 2009</td>
<td>Release Engineers send announcement email to
developers with a rough schedule for the FreeBSD
&local.rel; release.</td>
</tr>
<tr>
<td>Announce the Ports Freeze</td>
<td>3 April 2009</td>
<td>3 April 2009</td>
<td>Someone from <tt>portmgr@</tt> should email
<tt>freebsd-ports@</tt> to set a date
for the week long ports freeze and tagging of the ports tree.</td>
</tr>
<tr>
<td>Code freeze begins</td>
<td>23 March 2009</td>
<td>23 March 2009</td>
<td>After this date, all commits to RELENG_7 must be approved by <a
href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>. Certain highly
active documentation committers are exempt from this rule for
routine man page / release note updates. Heads-up emails
should be sent to the developers, as well as <tt>stable@</tt>
and <tt>qa@</tt> lists.</td>
</tr>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td>Announce <tt>doc/</tt> tree slush</td>
<td>--</td>
<td>3 April 2009</td>
<td>Notification of the impending <tt>doc/</tt> tree slush should
be sent to <tt>doc@</tt>.</td>
</tr>
<tr>
<td>Ports tree frozen</td>
<td>13 April 2009</td>
<td>13 April 2009</td>
<td>Only approved commits will be permitted to the <tt>ports/</tt>
tree during the freeze.</td>
</tr>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td><tt>doc/</tt> tree slush</td>
<td>10 April 2009</td>
<td>10 April 2009</td>
<td>Non-essential commits to the <tt>en_US.ISO8859-1/</tt> subtree
should be delayed from this point until after the <tt>doc/</tt>
tree tagging, to give translation teams time to synchronize
their work.</td>
</tr>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td><tt>doc/</tt> tree tagged.</td>
<td>17 April 2009</td>
<td>17 April 2009</td>
<td>Version number bumps for <tt>doc/</tt> subtree.
<tt>RELEASE_&local.rel.tag;_0</tt> tag for <tt>doc/</tt>. <tt>doc/</tt>
slush ends at this time.</td>
</tr>
<tr>
<td><tt>BETA1</tt> builds</td>
<td>30 March 2009</td>
<td>31 March 2009</td>
<td>Begin BETA1 builds.</td>
</tr>
<tr>
<td><tt>RELENG_7_2</tt> branch</td>
<td>10 April 2009</td>
<td>15 April 2009</td>
<td>The new release branch is created. Update <tt>newvers.sh</tt>
and <tt>release.ent</tt> on various branches involved.</td>
</tr>
<tr>
<td><tt>RC1</tt> builds</td>
<td>13 April 2009</td>
<td>15 April 2009</td>
<td>Begin RC1 builds.</td>
</tr>
<!-- portmgr should tweak these values after we commit it to CVS -->
<!-- packages should be loaded on ftp-master at least two days before -->
<!-- release bits get loaded to avoid network congestion problems -->
<tr>
<td>Ports tree tagged</td>
<td>20 April 2009</td>
<td>21 April 2009</td>
<td><tt>RELEASE_&local.rel.tag;_0</tt> tag for <tt>ports/</tt>.</td>
</tr>
<tr>
<td>Ports tree unfrozen</td>
<td>20 April 2009</td>
<td>21 April 2009</td>
<td>After the <tt>ports/</tt> tree is tagged,
the <tt>ports/</tt> tree will be re-opened for commits, but
commits made after tagging will not go in &local.rel;-RELEASE.</td>
</tr>
<tr>
<td>Final package build starts</td>
<td>20 April 2009</td>
<td>21 April 2009</td>
<td>The ports cluster and
<a href="http://pointyhat.FreeBSD.org">pointyhat</a>
build final packages.</td>
</tr>
<tr>
<td><tt>RC2</tt> builds</td>
<td>20 April 2009</td>
<td>23 April 2009</td>
<td>Begin RC2 builds.</td>
</tr>
<tr>
<td><tt>RELEASE</tt> builds</td>
<td>1 May 2009</td>
<td>1 May 2009</td>
<td>Begin RELEASE builds.</td>
</tr>
<tr>
<td>Announcement</td>
<td>4 May 2009</td>
<td>4 May 2009</td>
<td>Announcement sent out after a majority of the mirrors have
received the bits.</td>
</tr>
<tr>
<td>Turn over to the secteam</td>
<td>TBD</td>
<td>--</td>
<td>RELENG_&local.rel.tag; branch is handed over to
the FreeBSD Security Officer Team in one or two weeks after the
announcement.</td>
</tr>
</table>
<h1>Additional Information</h1>
<ul>
<!--
<li><a href="todo.html">FreeBSD &local.rel; developer todo list.</a></li>
<li><a href="approvals.html">FreeBSD &local.rel; Code Freeze Commit Approval List.</a></li>
-->
<li><a href="&base;/releng/index.html">FreeBSD Release Engineering website</a></li>
</ul>
&footer;
</body>
</html>
|
