blob: c3baee006f6876d2d223b9e507c6135233ae3e37 (
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
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
|
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD: www/en/releases/4.8R/schedule.sgml,v 1.11 2005/10/04 06:52:22 murray Exp $">
<!ENTITY local.rel "4.8">
<!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 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><td>Action</td><td>Expected</td><td>Actual</td><td>Description</td>
</tr>
<tr>
<td>Reminder announcement</td>
<td>16 Jan 2003</td>
<td>16 Jan 2003</td>
<td>Release Engineers send announcement email to
<tt>developers@FreeBSD.org</tt> with a rough schedule for the FreeBSD
&local.rel; release.</td>
</tr>
<tr>
<td>Another Reminder announcement</td>
<td>7 Feb 2003</td>
<td>10 Feb 2003</td>
<td>1 week reminder.</td>
</tr>
<tr>
<td>Another Reminder announcement</td>
<td>14 Feb 2003</td>
<td>14 Feb 2003</td>
<td>Final reminder, with exact time that freeze begins.</td>
</tr>
<tr>
<td>&local.rel;-PRERELEASE Testing Guide published</td><td>15 Feb 2003</td><td>2 Mar 2003</td>
<td>A <a href="&base;/releases/&local.rel;R/qa.html">testing guide</a>
should be published with information about recent changes and
areas of the system that should be thoroughly tested during the
pre-release/RC period.</td>
</tr>
<tr>
<td><tt>&local.rel;-PRERELEASE</tt></td>
<td>15 Feb 2003</td>
<td>15 Feb 2003</td>
<td><tt>newvers.sh</tt>, and <tt>release.ent</tt> updated.</td>
</tr>
<tr>
<td>FTP site updated</td>
<td>15 Feb 2003</td>
<td><i>unnecessary</i></td>
<td><tt>pkg_add -r</tt> works for <tt>&local.rel;-PRERELEASE</tt> machines.</td>
</tr>
<tr>
<td>Code freeze begins</td>
<td>15 Feb 2003</td>
<td>15 Feb 2003</td>
<td>After this date, all commits to the <tt>RELENG_4</tt> branch
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 <tt>developers@</tt>, <tt>stable@</tt> and <tt>qa@</tt> lists.</td>
</tr>
<tr>
<td><tt>&local.rel;-RC</tt></td>
<td>1 Mar 2003</td>
<td>2 Mar 2003</td>
<td><tt>newvers.sh</tt> and <tt>release.ent</tt> updated.</td>
</tr>
<tr>
<td>Announce the Ports Freeze</td>
<td>1 Mar 2003</td>
<td>1 Mar 2003</td>
<td>Someone from <tt>portmgr@</tt> should email
<tt>freebsd-ports@</tt> and BCC: <tt>developers@</tt> to set a date
for the week long ports freeze and tagging of the ports tree.</td>
</tr>
<tr>
<td>First release candidate</td>
<td>1 Mar 2003</td>
<td>3 Mar 2003</td>
<td>The first release candidate for the x86 and Alpha architecture is
released. ISO images should be uploaded to
<tt>ftp-master.FreeBSD.org</tt> and
<tt>releng4.FreeBSD.org</tt>. A network install directory should
be uploaded to <tt>ftp-master.FreeBSD.org</tt>. The
<tt>packages/</tt> directory should be a <em>relative</em> symlink,
as described in the releng article.
</tr>
<tr>
<td>Heads up to <tt>-stable</tt></td>
<td>2 Mar 2003</td>
<td>3 Mar 2003</td>
<td>A message should be sent to <tt>qa@FreeBSD.org</tt> and
<tt>stable@FreeBSD.org</tt> after the snapshot is uploaded.</td>
</tr>
<tr>
<td>Second release candidate</td>
<td>16 Mar 2003</td>
<td>17 Mar 2003</td>
<td>Note: the release date of this candidate depends on the user
experience with RC1.</td>
</tr>
<tr>
<td>Third release candidate</td>
<td>--</td>
<td>--</td>
<td></td>
</tr>
<!-- portmgr should tweak these values after we commit it to CVS -->
<tr>
<td>Ports tree frozen</td>
<td>5 Mar 2003</td>
<td>6 Mar 2003</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>Announce <tt>doc/</tt> tree slush</td>
<td>6 Mar 2003</td>
<td>7 Mar 2003</td>
<td>Notification of the impending <tt>doc/</tt> tree slush should
be sent to <tt>doc@</tt>.</td>
</tr>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td><tt>doc/</tt> tree slush</td>
<td>10 Mar 2003</td>
<td>10 Mar 2003</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>
<!-- portmgr should tweak these values after we commit it to CVS -->
<tr>
<td>Ports tree tagged</td>
<td>13 Mar 2003</td>
<td>--</td>
<td><tt>RELEASE_4_8_0</tt> tag for <tt>ports/</tt>.</td>
</tr>
<tr>
<td>Ports tree unfrozen</td>
<td>22 Mar 2003</td>
<td>22 Mar 2003</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>20 Mar 2003</td>
<td>--</td>
<td>The ports cluster and <a href="http://bento.FreeBSD.org">bento</a>
build final packages.</td>
</tr>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td><tt>doc/</tt> tree tagged.</td>
<td>19 Mar 2003</td>
<td>22 Mar 2003</td>
<td>Version number bumps for <tt>doc/</tt> subtree.
<tt>RELEASE_4_8_0</tt> tag for <tt>doc/</tt>. <tt>doc/</tt>
slush ends at this time.</td>
</tr>
<tr>
<td><tt>RELENG_4_8</tt> branch</td>
<td>22 Mar 2003</td>
<td>23 Mar 2003</td>
<td>The release branch is created.</td>
</tr>
<tr>
<td>Note to freebsd-stable@</td>
<td>22 Mar 2003</td>
<td>--</td>
<td>A note should be sent to the freebsd-stable@ list to let
over-anxious users know that the tags have been created but the
release still isn't ready. Tags may be slid before the
announcement goes out. Point users to freebsd-qa@ for
details.</td>
</tr>
<tr>
<td>Version numbers bumped.</td>
<td>23 Mar 2003</td>
<td>--</td>
<td>The files listed <a
href="&base;/doc/en_US.ISO8859-1/articles/releng/article.html#VERSIONBUMP">here</a>
are updated to reflect the fact that this is FreeBSD &local.rel;.</td>
</tr>
<tr>
<td>Update man.cgi on the website.</td>
<td>23 Mar 2003</td>
<td>28 Mar 2003</td>
<td>Make sure the &local.rel; manual pages are being displayed by default
for the man->web gateway. Also make sure these man pages are
pointed to by docs.sgml.</td>
</tr>
<tr>
<td>src tree tagged.</td>
<td>29 Mar 2003</td>
<td>--</td>
<td><tt>RELENG_4_8_0_RELEASE</tt> tag for <tt>src/</tt>.</td>
</tr>
<tr>
<td>Final builds.</td>
<td>29 Mar 2003</td>
<td>--</td>
<td>Final builds for x86 and Alpha in a pristine environment.</td>
</tr>
<tr>
<td>Warn <tt>hubs@FreeBSD.org</tt></td>
<td>29 Mar 2003</td>
<td>--</td>
<td>Heads up email to <a
href="mailto:hubs@FreeBSD.org">hubs@FreeBSD.org</a> 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>29 Mar 2003</td>
<td>--</td>
<td>Release and packages uploaded to <tt>ftp-master.FreeBSD.org</tt></td>
</tr>
<tr>
<td>Announcement</td>
<td>30 Mar 2003</td>
<td>--</td>
<td>Announcement sent out after a majority of the mirrors have
received the bits.</td>
</tr>
<tr>
<td>Unfreeze the tree</td>
<td>30 Mar 2003</td>
<td>--</td>
<td>Announcement to <tt>developers@</tt> explaining that the release is
out, and commits to <tt>RELENG_4</tt> no longer require approval. Also
note the policy for commits to the <tt>RELENG_4_8</tt> branch.</td>
</tr>
</table>
&footer;
</body>
</html>
|
