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
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD: www/en/releases/5.5R/schedule.sgml,v 1.11 2006/05/25 20:23:56 bmah Exp $">
<!ENTITY local.rel "5.5">
<!ENTITY local.rel.tag "5_5">
<!ENTITY title "FreeBSD &local.rel; Release Process">
<!ENTITY % navincludes SYSTEM "../../includes.navdownload.sgml"> %navincludes;
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<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 release engineering process or
quality assurance issues should be sent to the public <a
href="mailto:FreeBSD-qa@FreeBSD.org">freebsd-qa</a> mailing list.
<a
href="&base;/doc/en_US.ISO8859-1/books/faq/misc.html#DEFINE-MFC">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">
<th>Action</th>
<th>Expected</th>
<th>Actual</th>
<th>Description</th>
</tr>
<tr>
<td>Reminder announcement</td>
<td>--</td>
<td>25 January 2006</td>
<td>Release Engineers send announcement email to
developers with a rough schedule for the FreeBSD
&local.rel; release.</td>
</tr>
<tr>
<td>Code freeze begins</td>
<td>31 January 2006</td>
<td>31 January 2006</td>
<td>After this date, all commits to HEAD 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>
<tr>
<td>Announce the Ports Freeze</td>
<td>--</td>
<td>5 February 2006</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>Begin <tt>&local.rel;-BETA1</tt> builds</td>
<td>5 February 2006</td>
<td>5 February 2006</td>
<td>Begin building the first public test release build for all Tier-1
platforms.</td>
</tr>
<tr>
<td>Release <tt>&local.rel;-BETA1</tt></td>
<td>5 February 2006</td>
<td>5 February 2006</td>
<td>&local.rel;-BETA1 tier-1 platform images built, released, and
uploaded to <tt>ftp-master.FreeBSD.org</tt>.</td>
</tr>
<tr>
<td>Begin <tt>&local.rel;-BETA2</tt> builds</td>
<td>19 February 2006</td>
<td>16 February 2006</td>
<td>Begin building the second public test release build for all Tier-1
platforms.</td>
</tr>
<tr>
<td>Release <tt>&local.rel;-BETA2</tt></td>
<td>19 February 2006</td>
<td>20 February 2006</td>
<td>&local.rel;-BETA2 tier-1 platform images built, released, and
uploaded to <tt>ftp-master.FreeBSD.org</tt>.</td>
</tr>
<!-- portmgr should tweak these values after we commit it to CVS -->
<tr>
<td>Ports tree frozen</td>
<td>20 February 2006</td>
<td>23 February 2006</td>
<td>Only approved commits will be permitted to the <tt>ports/</tt>
tree during the freeze.</td>
</tr>
<tr>
<td>Begin <tt>&local.rel;-BETA3</tt> builds</td>
<td>5 March 2006</td>
<td>1 March 2006</td>
<td>Begin building the third public test release build for all Tier-1
platforms.</td>
</tr>
<tr>
<td>Release <tt>&local.rel;-BETA3</tt></td>
<td>5 March 2006</td>
<td>5 March 2006</td>
<td>&local.rel;-BETA3 tier-1 platform images built, released, and
uploaded to <tt>ftp-master.FreeBSD.org</tt>.</td>
</tr>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td>Announce <tt>doc/</tt> tree slush</td>
<td>6 March 2006</td>
<td>6 March 2006</td>
<td>Notification of the impending <tt>doc/</tt> tree slush should
be sent to <tt>doc@</tt>.</td>
</tr>
<tr>
<td>Begin <tt>&local.rel;-BETA4</tt> builds</td>
<td>--</td>
<td>14 March 2006</td>
<td>Begin building the fourth public test release build for all Tier-1
platforms.</td>
</tr>
<tr>
<td>Release <tt>&local.rel;-BETA4</tt></td>
<td>--</td>
<td>14 March 2006</td>
<td>&local.rel;-BETA4 tier-1 platform images built, released, and
uploaded to <tt>ftp-master.FreeBSD.org</tt>.</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>6 March 2006</td>
<td>14 March 2006</td>
<td><tt>RELEASE_&local.rel.tag;_0</tt> tag for <tt>ports/</tt>.</td>
</tr>
<tr>
<td>Ports tree unfrozen</td>
<td>6 March 2006</td>
<td>14 March 2006</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>TBD</td>
<td>--</td>
<td>The ports cluster and
<a href="http://pointyhat.FreeBSD.org">pointyhat</a>
build final packages.</td>
</tr>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td><tt>doc/</tt> tree slush</td>
<td>10 March 2006</td>
<td>7 April 2006</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>13 March 2006</td>
<td>21 May 2006</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>RELENG_5_5</tt> branch</td>
<td><strike>19 March 2006</strike><br>
12 May 2006</td>
<td>12 May 2006</td>
<td>The new major version branch is created. Update <tt>newvers.sh</tt>
and <tt>release.ent</tt> on various branches involved.</td>
</tr>
<tr>
<td><tt>src/</tt> unfrozen</td>
<td>TBD</td>
<td>--</td>
<td>Unfreeze <tt>RELENG_5</tt> src. Continue to coordinate significant
check-ins with <tt>re@FreeBSD.org</tt> until the release is final.</td>
</tr>
<tr>
<td>Build <tt>&local.rel;-RC1</tt></td>
<td><strike>19 March 2006</strike><br>
14 May 2006</td>
<td>13 May 2006</td>
<td>Begin building the first release candidate build for all Tier-1
platforms.</td>
</tr>
<tr>
<td>Release <tt>&local.rel;-RC1</tt></td>
<td><strike>19 March 2006</strike><br>
14 May 2006</td>
<td>16 May 2006</td>
<td>&local.rel;-RC1 tier-1 platform images released, and
uploaded to <tt>ftp-master.FreeBSD.org</tt>.</td>
</tr>
<tr>
<td>Version numbers bumped</td>
<td><strike>31 March 2006</strike><br>
20 May 2006</td>
<td>12 May 2006</td>
<td>The files listed <a
href="&base;/doc/en_US.ISO8859-1/articles/releng/article.html#VERSIONBUMP">here</a>
are updated to reflect FreeBSD &local.rel;.</td>
</tr>
<tr>
<td><tt>src/</tt> tree tagged</td>
<td><strike>31 March 2006</strike><br>
20 May 2006</td>
<td>22 May 2006</td>
<td>Tag the <tt>RELENG_&local.rel.tag;</tt> branch with
<tt>RELENG_&local.rel.tag;_0_RELEASE</tt>.</td>
</tr>
<tr>
<td>Begin <tt>&local.rel;-RELEASE</tt> builds</td>
<td><strike>31 March 2006</strike><br>
20 May 2006</td>
<td>22 May 2006</td>
<td>Start &local.rel;-RELEASE Tier-1 builds.</td>
</tr>
<tr>
<td>Warn <tt>mirror-announce@FreeBSD.org</tt></td>
<td><strike>31 March 2006</strike><br>
20 May 2006</td>
<td>23 May 2006</td>
<td>Heads up email to <tt>mirror-announce@FreeBSD.org</tt> to give admins
time to prepare for the load spike to come. The site
administrators have frequently requested advance notice
for new ISOs.</td>
</tr>
<tr>
<td>Upload to <tt>ftp-master</tt></td>
<td><strike>2 April 2006</strike><br>
21 May 2006</td>
<td>24 May 2006</td>
<td>Release and packages uploaded to <tt>ftp-master.FreeBSD.org.</tt></td>
</tr>
<tr>
<td>Announcement</td>
<td><strike>3 April 2006</strike><br>
22 May 2006</td>
<td>25 May 2006</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>31 May 2006</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>
|