|
Lines 18-24
Link Here
|
| 18 |
|
18 |
|
| 19 |
<p>General discussions about the release engineering process or |
19 |
<p>General discussions about the release engineering process or |
| 20 |
quality assurance issues should be sent to the public <a |
20 |
quality assurance issues should be sent to the public <a |
| 21 |
href="mailto:freebsd-qa@FreeBSD.org">freebsd-qa</a> mailing list. |
21 |
href="mailto:FreeBSD-qa@FreeBSD.org">FreeBSD-qa</a> mailing list. |
| 22 |
<a |
22 |
<a |
| 23 |
href="&base;/doc/en_US.ISO8859-1/books/faq/misc.html#DEFINE-MFC">MFC</a> |
23 |
href="&base;/doc/en_US.ISO8859-1/books/faq/misc.html#DEFINE-MFC">MFC</a> |
| 24 |
requests should be sent to <a |
24 |
requests should be sent to <a |
|
Lines 30-42
Link Here
|
| 30 |
<tr><td>Action</td><td>Expected</td><td>Actual</td><td>Description</td> |
30 |
<tr><td>Action</td><td>Expected</td><td>Actual</td><td>Description</td> |
| 31 |
</tr> |
31 |
</tr> |
| 32 |
<tr> |
32 |
<tr> |
| 33 |
<td>Reminder announcement</td><td>06 Aug 2002</td><td>06 Aug 2002</td> |
33 |
<td>Reminder announcement</td> |
|
|
34 |
<td>06 Aug 2002</td> |
| 35 |
<td>06 Aug 2002</td> |
| 34 |
<td>Release Engineers send announcement email to |
36 |
<td>Release Engineers send announcement email to |
| 35 |
developers@FreeBSD.org with a rough schedule for the FreeBSD 4.7 |
37 |
<tt>developers@FreeBSD.org</tt> with a rough schedule for the FreeBSD 4.7 |
| 36 |
release.</td> |
38 |
release.</td> |
| 37 |
</tr> |
39 |
</tr> |
| 38 |
<tr> |
40 |
<tr> |
| 39 |
<td>4.7-PRERELEASE Testing Guide published</td><td>Ongoing</td><td>02 Sep 2002</td> |
41 |
<td><tt>4.7-PRERELEASE</tt> Testing Guide published</td> |
|
|
42 |
<td>Ongoing</td> |
| 43 |
<td>02 Sep 2002</td> |
| 40 |
<td>A <a href="&base;/releases/4.7R/qa.html">testing guide</a> |
44 |
<td>A <a href="&base;/releases/4.7R/qa.html">testing guide</a> |
| 41 |
should be published with information about recent changes and |
45 |
should be published with information about recent changes and |
| 42 |
areas of the system that should be thoroughly tested during the |
46 |
areas of the system that should be thoroughly tested during the |
|
Lines 44-51
Link Here
|
| 44 |
</tr> |
48 |
</tr> |
| 45 |
<tr> |
49 |
<tr> |
| 46 |
<td><tt>4.7-PRERELEASE</tt></td> |
50 |
<td><tt>4.7-PRERELEASE</tt></td> |
| 47 |
<td>01 Sep 2002</td> |
51 |
<td>01 Sep 2002</td> |
| 48 |
<td>02 Sep 2002</td> |
52 |
<td>02 Sep 2002</td> |
| 49 |
<td><tt>newvers.sh</tt>, and <tt>release.ent</tt> updated.</td> |
53 |
<td><tt>newvers.sh</tt>, and <tt>release.ent</tt> updated.</td> |
| 50 |
</tr> |
54 |
</tr> |
| 51 |
<tr> |
55 |
<tr> |
|
Lines 64-70
Link Here
|
| 64 |
href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>. Certain highly |
68 |
href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>. Certain highly |
| 65 |
active documentation committers are exempt from this rule for |
69 |
active documentation committers are exempt from this rule for |
| 66 |
routine man page / release note updates. Heads-up emails |
70 |
routine man page / release note updates. Heads-up emails |
| 67 |
should be sent to the developers@, stable@, and qa@ lists.</td> |
71 |
should be sent to the <tt>developers@</tt>, <tt>stable@</tt> |
|
|
72 |
and <tt>qa@</tt> lists.</td> |
| 68 |
</tr> |
73 |
</tr> |
| 69 |
|
74 |
|
| 70 |
<tr> |
75 |
<tr> |
|
Lines 88-94
Link Here
|
| 88 |
<td>16 Sep 2002</td> |
93 |
<td>16 Sep 2002</td> |
| 89 |
<td>Someone from <tt>portmgr</tt> should email |
94 |
<td>Someone from <tt>portmgr</tt> should email |
| 90 |
<tt>freebsd-ports@</tt> and BCC: <tt>developers@</tt> to set a date |
95 |
<tt>freebsd-ports@</tt> and BCC: <tt>developers@</tt> to set a date |
| 91 |
for the week long ports freeze and tagging of the ports tree.</td> |
96 |
for the week long ports freeze and tagging of the <tt>ports/</tt> tree.</td> |
| 92 |
</tr> |
97 |
</tr> |
| 93 |
|
98 |
|
| 94 |
<tr> |
99 |
<tr> |
|
Lines 100-106
Link Here
|
| 100 |
<tt>ftp-master.freebsd.org</tt> and |
105 |
<tt>ftp-master.freebsd.org</tt> and |
| 101 |
<tt>releng4.freebsd.org</tt>. A network install directory should |
106 |
<tt>releng4.freebsd.org</tt>. A network install directory should |
| 102 |
be uploaded to <tt>ftp-master.freebsd.org</tt>. The |
107 |
be uploaded to <tt>ftp-master.freebsd.org</tt>. The |
| 103 |
<tt>packages</tt> directory should be a <em>relative</em> symlink, |
108 |
<tt>packages/</tt> directory should be a <em>relative</em> symlink, |
| 104 |
as described in the releng article. |
109 |
as described in the releng article. |
| 105 |
</tr> |
110 |
</tr> |
| 106 |
|
111 |
|
|
Lines 119-125
Link Here
|
| 119 |
|
124 |
|
| 120 |
<td>The proposed package split (which packages go on which disc of |
125 |
<td>The proposed package split (which packages go on which disc of |
| 121 |
the 4 CD set) should be posted to <tt>qa@FreeBSD.org</tt>, |
126 |
the 4 CD set) should be posted to <tt>qa@FreeBSD.org</tt>, |
| 122 |
<tt>ports@FreeBSD.org</tt>, and <tt>stable@FreeBSD.org</tt>.</td> |
127 |
<tt>ports@FreeBSD.org</tt> and <tt>stable@FreeBSD.org</tt>.</td> |
| 123 |
|
128 |
|
| 124 |
</tr> |
129 |
</tr> |
| 125 |
|
130 |
|
|
Lines 159-169
Link Here
|
| 159 |
<td>05 Oct 2002</td> |
164 |
<td>05 Oct 2002</td> |
| 160 |
<td>After the <tt>ports</tt> tree is tagged, |
165 |
<td>After the <tt>ports</tt> tree is tagged, |
| 161 |
the <tt>ports/</tt> tree will be re-opened for commits, but |
166 |
the <tt>ports/</tt> tree will be re-opened for commits, but |
| 162 |
commits made after tagging will not go in 4.7-RELEASE.</td> |
167 |
commits made after tagging will not go in <tt>4.7-RELEASE</tt>.</td> |
| 163 |
</tr> |
168 |
</tr> |
| 164 |
|
169 |
|
| 165 |
<tr> |
170 |
<tr> |
| 166 |
<td>Final package build starts |
171 |
<td>Final package build starts</td> |
| 167 |
<td>25 Sep 2002</td> |
172 |
<td>25 Sep 2002</td> |
| 168 |
<td>05 Oct 2002</td> |
173 |
<td>05 Oct 2002</td> |
| 169 |
<td>The ports cluster and <a href="http://bento.FreeBSD.org">bento</a> |
174 |
<td>The ports cluster and <a href="http://bento.FreeBSD.org">bento</a> |
|
Lines 179-185
Link Here
|
| 179 |
popular packages appearing on the first disc.</td> |
184 |
popular packages appearing on the first disc.</td> |
| 180 |
</tr> |
185 |
</tr> |
| 181 |
<tr> |
186 |
<tr> |
| 182 |
<td>doc tree tagged.</td> |
187 |
<td><tt>doc/</tt> tree tagged.</td> |
| 183 |
<td>27 Sep 2002</td> |
188 |
<td>27 Sep 2002</td> |
| 184 |
<td>01 Oct 2002</td> |
189 |
<td>01 Oct 2002</td> |
| 185 |
<td><tt>RELEASE_4_7_0</tt> tag for docs.</td> |
190 |
<td><tt>RELEASE_4_7_0</tt> tag for docs.</td> |
|
Lines 193-205
Link Here
|
| 193 |
</tr> |
198 |
</tr> |
| 194 |
|
199 |
|
| 195 |
<tr> |
200 |
<tr> |
| 196 |
<td>Note to freebsd-stable@</td> |
201 |
<td>Note to <tt>freebsd-stable@</tt></td> |
| 197 |
<td>28 Sep 2002</td> |
202 |
<td>28 Sep 2002</td> |
| 198 |
<td>06 Oct 2002</td> |
203 |
<td>06 Oct 2002</td> |
| 199 |
<td>A note should be sent to the freebsd-stable@ list to let |
204 |
<td>A note should be sent to the <tt>freebsd-stable@</tt> list to let |
| 200 |
over-anxious users know that the tags have been created but the |
205 |
over-anxious users know that the tags have been created but the |
| 201 |
release still isn't ready. Tags may be slid before the |
206 |
release still isn't ready. Tags may be slid before the |
| 202 |
announcement goes out. Point users to freebsd-qa@ for |
207 |
announcement goes out. Point users to <tt>freebsd-qa@</tt> for |
| 203 |
details.</td> |
208 |
details.</td> |
| 204 |
</tr> |
209 |
</tr> |
| 205 |
|
210 |
|
|
Lines 265-273
Link Here
|
| 265 |
<td>Unfreeze the tree</td> |
270 |
<td>Unfreeze the tree</td> |
| 266 |
<td>08 Oct 2002</td> |
271 |
<td>08 Oct 2002</td> |
| 267 |
<td>10 Oct 2002</td> |
272 |
<td>10 Oct 2002</td> |
| 268 |
<td>Announcement to developers@ explaining that the release is |
273 |
<td>Announcement to <tt>developers@</tt> explaining that the release is |
| 269 |
out, and commits to RELENG_4 no longer require approval. Also |
274 |
out, and commits to <tt>RELENG_4</tt> no longer require approval. Also |
| 270 |
note the policy for commits to the RELENG_4_7 branch.</td> |
275 |
note the policy for commits to the <tt>RELENG_4_7</tt> branch.</td> |
| 271 |
</tr> |
276 |
</tr> |