aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/htdocs/releases/6.3R/schedule.xml
blob: 0bf4a2f94542eae33e87c7482641e2f5bf662788 (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
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN"
"http://www.FreeBSD.org/XML/doc/share/sgml/xhtml10-freebsd.dtd" [
<!ENTITY email 'freebsd-qa'>
<!ENTITY local.rel "6.3">
<!ENTITY local.rel.tag "6_3">
<!ENTITY title "FreeBSD &local.rel; Release Process">
]>

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
      <title>&title;</title>

      <cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
    </head>

    <body class="navinclude.download">

<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">
    <td>Action</td>
    <td>Expected</td>
    <td>Actual</td>
    <td>Description</td>
  </tr>

  <tr>
    <td>Reminder announcement</td>
    <td>TBD</td>
    <td>15&nbsp;Oct&nbsp;2007</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>23&nbsp;Oct&nbsp;2007</td>
    <td>23&nbsp;Oct&nbsp;2007</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>18&nbsp;Nov&nbsp;2007</td>
    <td>18&nbsp;Nov&nbsp;2007</td>
    <td>After this date, all commits to RELENG_6 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>TBD</td>
    <td>19&nbsp;Nov&nbsp;2007</td>
    <td>Notification of the impending <tt>doc/</tt> tree slush should
      be sent to <tt>doc@</tt>.</td>
  </tr>

<!-- portmgr should tweak these values after we commit it to CVS -->
  <tr>
    <td>Ports tree frozen</td>
    <td>30&nbsp;Oct&nbsp;2007</td>
    <td>30&nbsp;Oct&nbsp;2007</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>25&nbsp;Nov&nbsp;2007</td>
    <td>25&nbsp;Nov&nbsp;2007</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>5&nbsp;Dec&nbsp;2007</td>
    <td>5&nbsp;Dec&nbsp;2007</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>24&nbsp;Oct&nbsp;2007</td>
    <td>1&nbsp;Nov&nbsp;2007</td>
    <td>Begin BETA1 builds.</td>
  </tr>

  <tr>
    <td><tt>BETA2</tt> builds</td>
    <td>7&nbsp;Nov&nbsp;2007</td>
    <td>9&nbsp;Nov&nbsp;2007</td>
    <td>Begin BETA2 builds.</td>
  </tr>

  <tr>
    <td><tt>RELENG_6_3</tt> branch</td>
    <td>21&nbsp;Nov&nbsp;2007</td>
    <td>25&nbsp;Nov&nbsp;2007</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>21&nbsp;Nov&nbsp;2007</td>
    <td>26&nbsp;Nov&nbsp;2007</td>
    <td>Begin RC1 builds.</td>
  </tr>

  <tr>
    <td><tt>RC2</tt> builds</td>
    <td>5&nbsp;Dec&nbsp;2007</td>
    <td>22&nbsp;Dec&nbsp;2007</td>
    <td>Begin RC2 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>14&nbsp;Dec&nbsp;2007</td>
    <td>11&nbsp;Dec&nbsp;2007</td>
    <td><tt>RELEASE_&local.rel.tag;_0</tt> tag for <tt>ports/</tt>.</td>
  </tr>

  <tr>
    <td>Ports tree unfrozen</td>
    <td>14&nbsp;Dec&nbsp;2007</td>
    <td>11&nbsp;Dec&nbsp;2007</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>14&nbsp;Dec&nbsp;2007</td>
    <td>12&nbsp;Dec&nbsp;2007</td>
    <td>The ports cluster and
      <a href="http://pointyhat.FreeBSD.org">pointyhat</a>
      build final packages.</td>
  </tr>

  <tr>
    <td><tt>RELEASE</tt> builds</td>
    <td>19&nbsp;Dec&nbsp;2007</td>
    <td>15&nbsp;Jan&nbsp;2008</td>
    <td>Begin RELEASE builds.</td>
  </tr>

  <tr>
    <td>Announcement</td>
    <td>23&nbsp;Dec&nbsp;2007</td>
    <td>18&nbsp;Jan&nbsp;2008</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>28&nbsp;Jan&nbsp;2008</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="&base;/releng/index.html">FreeBSD Release Engineering website.</a></li>
</ul>


  </body>
</html>