|
Lines 19-25
Link Here
|
| 19 |
|
19 |
|
| 20 |
<p>General discussions about the release engineering process or |
20 |
<p>General discussions about the release engineering process or |
| 21 |
quality assurance issues should be sent to the public <a |
21 |
quality assurance issues should be sent to the public <a |
| 22 |
href="mailto:freebsd-qa@FreeBSD.org">freebsd-qa</a> mailing list. |
22 |
href="mailto:FreeBSD-qa@FreeBSD.org">freebsd-qa</a> mailing list. |
| 23 |
<a |
23 |
<a |
| 24 |
href="&base;/doc/en_US.ISO8859-1/books/faq/misc.html#DEFINE-MFC">MFC</a> |
24 |
href="&base;/doc/en_US.ISO8859-1/books/faq/misc.html#DEFINE-MFC">MFC</a> |
| 25 |
requests should be sent to <a |
25 |
requests should be sent to <a |
|
Lines 35-41
Link Here
|
| 35 |
<td>16 Jan 2003</td> |
35 |
<td>16 Jan 2003</td> |
| 36 |
<td>16 Jan 2003</td> |
36 |
<td>16 Jan 2003</td> |
| 37 |
<td>Release Engineers send announcement email to |
37 |
<td>Release Engineers send announcement email to |
| 38 |
developers@FreeBSD.org with a rough schedule for the FreeBSD |
38 |
<tt>developers@FreeBSD.org</tt> with a rough schedule for the FreeBSD |
| 39 |
&local.rel; release.</td> |
39 |
&local.rel; release.</td> |
| 40 |
</tr> |
40 |
</tr> |
| 41 |
<tr> |
41 |
<tr> |
|
Lines 79-85
Link Here
|
| 79 |
href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>. Certain highly |
79 |
href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>. Certain highly |
| 80 |
active documentation committers are exempt from this rule for |
80 |
active documentation committers are exempt from this rule for |
| 81 |
routine man page / release note updates. Heads-up emails |
81 |
routine man page / release note updates. Heads-up emails |
| 82 |
should be sent to the developers@, stable@, and qa@ lists.</td> |
82 |
should be sent to the <tt>developers@</tt>, <tt>stable@</tt> and <tt>qa@</tt> lists.</td> |
| 83 |
</tr> |
83 |
</tr> |
| 84 |
|
84 |
|
| 85 |
<tr> |
85 |
<tr> |
|
Lines 107-118
Link Here
|
| 107 |
<tt>ftp-master.freebsd.org</tt> and |
107 |
<tt>ftp-master.freebsd.org</tt> and |
| 108 |
<tt>releng4.freebsd.org</tt>. A network install directory should |
108 |
<tt>releng4.freebsd.org</tt>. A network install directory should |
| 109 |
be uploaded to <tt>ftp-master.freebsd.org</tt>. The |
109 |
be uploaded to <tt>ftp-master.freebsd.org</tt>. The |
| 110 |
<tt>packages</tt> directory should be a <em>relative</em> symlink, |
110 |
<tt>packages/</tt> directory should be a <em>relative</em> symlink, |
| 111 |
as described in the releng article. |
111 |
as described in the releng article. |
| 112 |
</tr> |
112 |
</tr> |
| 113 |
|
113 |
|
| 114 |
<tr> |
114 |
<tr> |
| 115 |
<td>Heads up to -stable</td> |
115 |
<td>Heads up to <tt>-stable</tt></td> |
| 116 |
<td>2 Mar 2003</td> |
116 |
<td>2 Mar 2003</td> |
| 117 |
<td>3 Mar 2003</td> |
117 |
<td>3 Mar 2003</td> |
| 118 |
<td>A message should be sent to <tt>qa@FreeBSD.org</tt> and |
118 |
<td>A message should be sent to <tt>qa@FreeBSD.org</tt> and |
|
Lines 122-128
Link Here
|
| 122 |
<tr> |
122 |
<tr> |
| 123 |
<td>Second release candidate</td> |
123 |
<td>Second release candidate</td> |
| 124 |
<td>16 Mar 2003</td> |
124 |
<td>16 Mar 2003</td> |
| 125 |
<td>--</td> |
125 |
<td>17 Mar 2003</td> |
| 126 |
<td>Note: the release date of this candidate depends on the user |
126 |
<td>Note: the release date of this candidate depends on the user |
| 127 |
experience with RC1.</td> |
127 |
experience with RC1.</td> |
| 128 |
</tr> |
128 |
</tr> |
|
Lines 174-181
Link Here
|
| 174 |
<tr> |
174 |
<tr> |
| 175 |
<td>Ports tree unfrozen</td> |
175 |
<td>Ports tree unfrozen</td> |
| 176 |
<td>22 Mar 2003</td> |
176 |
<td>22 Mar 2003</td> |
| 177 |
<td>--</td> |
177 |
<td>22 Mar 2003</td> |
| 178 |
<td>After the <tt>ports</tt> tree is tagged, |
178 |
<td>After the <tt>ports/</tt> tree is tagged, |
| 179 |
the <tt>ports/</tt> tree will be re-opened for commits, but |
179 |
the <tt>ports/</tt> tree will be re-opened for commits, but |
| 180 |
commits made after tagging will not go in &local.rel;-RELEASE.</td> |
180 |
commits made after tagging will not go in &local.rel;-RELEASE.</td> |
| 181 |
</tr> |
181 |
</tr> |
|
Lines 192-198
Link Here
|
| 192 |
<tr> |
192 |
<tr> |
| 193 |
<td><tt>doc/</tt> tree tagged.</td> |
193 |
<td><tt>doc/</tt> tree tagged.</td> |
| 194 |
<td>19 Mar 2003</td> |
194 |
<td>19 Mar 2003</td> |
| 195 |
<td>--</td> |
195 |
<td>22 Mar 2003</td> |
| 196 |
<td>Version number bumps for <tt>doc/</tt> subtree. |
196 |
<td>Version number bumps for <tt>doc/</tt> subtree. |
| 197 |
<tt>RELEASE_4_8_0</tt> tag for <tt>doc/</tt>. <tt>doc/</tt> |
197 |
<tt>RELEASE_4_8_0</tt> tag for <tt>doc/</tt>. <tt>doc/</tt> |
| 198 |
slush ends at this time.</td> |
198 |
slush ends at this time.</td> |
|
Lines 201-207
Link Here
|
| 201 |
<tr> |
201 |
<tr> |
| 202 |
<td><tt>RELENG_4_8</tt> branch</td> |
202 |
<td><tt>RELENG_4_8</tt> branch</td> |
| 203 |
<td>22 Mar 2003</td> |
203 |
<td>22 Mar 2003</td> |
| 204 |
<td>--</td> |
204 |
<td>23 Mar 2003</td> |
| 205 |
<td>The release branch is created.</td> |
205 |
<td>The release branch is created.</td> |
| 206 |
</tr> |
206 |
</tr> |
| 207 |
|
207 |
|
|
Lines 238-244
Link Here
|
| 238 |
<td>src tree tagged.</td> |
238 |
<td>src tree tagged.</td> |
| 239 |
<td>23 Mar 2003</td> |
239 |
<td>23 Mar 2003</td> |
| 240 |
<td>--</td> |
240 |
<td>--</td> |
| 241 |
<td><tt>RELENG_4_8_0_RELEASE</tt> tag for src.</td> |
241 |
<td><tt>RELENG_4_8_0_RELEASE</tt> tag for <tt>src/</tt>.</td> |
| 242 |
</tr> |
242 |
</tr> |
| 243 |
|
243 |
|
| 244 |
<tr> |
244 |
<tr> |
|
Lines 278-286
Link Here
|
| 278 |
<td>Unfreeze the tree</td> |
278 |
<td>Unfreeze the tree</td> |
| 279 |
<td>24 Mar 2003</td> |
279 |
<td>24 Mar 2003</td> |
| 280 |
<td>--</td> |
280 |
<td>--</td> |
| 281 |
<td>Announcement to developers@ explaining that the release is |
281 |
<td>Announcement to <tt>developers@</tt> explaining that the release is |
| 282 |
out, and commits to RELENG_4 no longer require approval. Also |
282 |
out, and commits to <tt>RELENG_4</tt> no longer require approval. Also |
| 283 |
note the policy for commits to the RELENG_4_8 branch.</td> |
283 |
note the policy for commits to the <tt>RELENG_4_8</tt> branch.</td> |
| 284 |
</tr> |
284 |
</tr> |