Gentoo Archives: gentoo-commits

From: "Chris Gianelloni (wolf31o2)" <wolf31o2@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/releng/release/2008.0: index.xml
Date: Thu, 24 Jan 2008 03:28:18
Message-Id: E1JHslC-0008A5-7q@stork.gentoo.org
1 wolf31o2 08/01/24 03:28:14
2
3 Added: index.xml
4 Log:
5 Adding an initial release page for 2008.0's upcoming release. This still needs a lot of updates, but it's a start.
6
7 Revision Changes Path
8 1.1 xml/htdocs/proj/en/releng/release/2008.0/index.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/releng/release/2008.0/index.xml?rev=1.1&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/releng/release/2008.0/index.xml?rev=1.1&content-type=text/plain
12
13 Index: index.xml
14 ===================================================================
15 <?xml version='1.0' encoding="UTF-8"?>
16 <?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>
17 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
18
19
20 <guide link="/proj/en/releng/release/2008.0/index.xml" disclaimer="draft">
21 <title>2008.0 Release Information</title>
22
23 <author title="Author">
24 <mail>wolf31o2</mail>
25 </author>
26
27 <abstract>
28 This document serves as the definitive source for the 2008.0 release.
29 </abstract>
30
31 <license/>
32
33 <version>1.0</version>
34 <date>23 Jan 2008</date>
35
36 <chapter>
37 <title>General Information</title>
38
39 <section>
40 <title>Contacts</title>
41 <body>
42
43 <ul>
44 <li>Release Operations: <mail>wolf31o2</mail></li>
45 <li>Documentation: <mail>nightmorph</mail></li>
46 <li>Infrastructure: <mail>robbat2</mail></li>
47 <li>PR: <mail>dberkholz</mail></li>
48 <li>Security: <mail>wolf31o2</mail></li>
49 </ul>
50
51 </body>
52 </section>
53
54 <section>
55 <title>Release Schedule</title>
56 <body>
57
58 <note>
59 This schedule is tentative in nature and may change without notice based on the
60 needs of the Release Engineering project and Gentoo, as a whole.
61 </note>
62
63 <table>
64 <tr>
65 <th>Milestone</th>
66 <th>Target Date</th>
67 <th>Description</th>
68 <th>Status</th>
69 </tr>
70 <tr>
71 <ti>Initial meeting</ti>
72 <ti>23 Jan 2008</ti>
73 <ti>Plan release schedule, initial features, and other pertinent information for
74 the upcoming release. A feature request is called after this meeting.</ti>
75 <ti>Completed</ti>
76 </tr>
77 <tr>
78 <ti>Feature request cut-off</ti>
79 <ti>30 Jan 2008</ti>
80 <ti>This is the cut-off date for feature requests. No feature requests will be
81 honored after this date, to give ample time for QA.</ti>
82 <ti>In Progress</ti>
83 </tr>
84 <tr>
85 <ti>Initial snapshot</ti>
86 <ti>1 Feb 2008</ti>
87 <ti>A snapshot is made from the tree which is used for building the release.
88 After this point, packages are added/updated in the snapshot only if it is
89 necessary due to the potential impact of the issue, such as security bugs, or
90 release-specific changes, such as an updated livecd-tools.</ti>
91 <ti>Not Completed</ti>
92 </tr>
93 <tr>
94 <ti>QA builds/testing</ti>
95 <ti>25 Feb 2008</ti>
96 <ti>Several builds of the release media are made on each architecture, with
97 modifications being made to the snapshot and the release building tools, as
98 necessary.</ti>
99 <ti>Not Completed</ti>
100 </tr>
101 <tr>
102 <ti>Doc updates</ti>
103 <ti>25 Feb 2008</ti>
104 <ti>All documentation updates are to be submitted to the Documentation Liaison
105 by this date for the upcoming release. Things that are commonly updated are the
106 kernel versions used, kernel command line options that have been added/removed,
107 and changes to the installation process.</ti>
108 <ti>Not Completed</ti>
109 </tr>
110 <tr>
111 <ti>Snapshot freeze (BETA)</ti>
112 <ti>25 Feb 2008</ti>
113 <ti>The snapshot is frozen to build an initial BETA release for wider testing
114 in the community. Once the BETA is released, the snapshot is unfrozen.</ti>
115 <ti>Not Completed</ti>
116 </tr>
117 <tr>
118 <ti>Handbook updated</ti>
119 <ti>29 Feb 2008</ti>
120 <ti>The updated Handbook tarballs for each architecture are due to be delivered
121 to Release Engineering for use on the BETA release.</ti>
122 <ti>Not Completed</ti>
123 </tr>
124 <tr>
125 <ti>BETA information</ti>
126 <ti>2 Mar 2008</ti>
127 <ti>The press release/news item for the BETA release is written and has been
128 submitted to Release Engineering for approval. The BETA checklist is completed
129 and ready for distribution.</ti>
130 <ti>Not Completed</ti>
131 </tr>
132 <tr>
133 <ti>BETA upload</ti>
134 <ti>2 Mar 2008</ti>
135 <ti>The BETA is uploaded to the release staging server for distribution under
136 the experimental directory on participating mirrors.</ti>
137 <ti>Not Completed</ti>
138 </tr>
139 <tr>
140 <ti>BETA release</ti>
141 <ti>3 Mar 2008</ti>
142 <ti>The BETA is publicly released. The front page is updated to reflect this and
143 notification is sent to news outlets.</ti>
144 <ti>Not Completed</ti>
145 </tr>
146 <tr>
147 <ti>Snapshot freeze (Final)</ti>
148 <ti>10 Mar 2008</ti>
149 <ti>This is the due date for the final snapshot. After this point, no updates
150 are made to the snapshot and the final build phase begins.</ti>
151 <ti>Not Completed</ti>
152 </tr>
153 <tr>
154 <ti>Doc updates</ti>
155 <ti>10 Mar 2008</ti>
156 <ti>Any additional changes to the Handbook must be submitted by this date. This
157 conicides with the snapshot freeze, so no changes will happen in the snapshot
158 post this date to ensure the accuracy of the Handbook.</ti>
159 <ti>Not Completed</ti>
160 </tr>
161 <tr>
162 <ti>Handbook updated</ti>
163 <ti>12 Mar 2008</ti>
164 <ti>The updated Handbook tarballs for each architecture are due to be delivered
165 to Release Engineering for use on the final release.</ti>
166 <ti>Not Completed</ti>
167 </tr>
168 <tr>
169 <ti>Media uploaded</ti>
170 <ti>15 Mar 2008</ti>
171 <ti>All release media is uploaded to the release staging server (poseidon) by
172 this date to be prepared for release.</ti>
173 <ti>Not Completed</ti>
174 </tr>
175 <tr>
176 <ti>Final preparation</ti>
177 <ti>16 Mar 2008</ti>
178 <ti>One final check is made of all release materials, DIGESTS files are signed,
179 and any additional tasks are completed.</ti>
180 <ti>Not Completed</ti>
181 </tr>
182 <tr>
183 <ti>Release handover</ti>
184 <ti>16 Mar 2008</ti>
185 <ti>Release Engineering makes one final check of all materials, then hands it
186 over to Infrastructure for staging and release.</ti>
187 <ti>Not Completed</ti>
188 </tr>
189 <tr>
190 <ti>Release</ti>
191 <ti>17 Mar 2008</ti>
192 <ti>All news items are committed, the release materials and Handbook are made
193 visible to the public, and Release Engineering takes a well-deserved break.</ti>
194 <ti>Not Completed</ti>
195 </tr>
196 </table>
197
198 </body>
199 </section>
200
201 <!-- <section>
202 <title>Architectures Releasing</title>
203 <body>
204
205 <p>
206 The following supported architectures are tentatively releasing 2008.0:
207 </p>
208
209 <table>
210 <tr>
211 <th>Architecture</th>
212 <th>Subarch(es)</th>
213 <th>Expected Components</th>
214 <th>Release Coordinator(s)</th>
215 </tr>
216 <tr>
217 <ti>alpha</ti>
218 <ti>alpha</ti>
219 <ti>InstallCDs, stages, Release Notes</ti>
220 <ti>kloeri</ti>
221 </tr>
222 <tr>
223 <ti>amd64</ti>
224 <ti>amd64</ti>
225 <ti>InstallCD, stages, LiveCD, Release Notes</ti>
226 <ti>kugelfang</ti>
227 </tr>
228 <tr>
229 <ti>hppa</ti>
230 <ti>hppa1.1, hppa2.0</ti>
231 <ti>InstallCDs, stages, Release Notes</ti>
232 <ti>dertobi123</ti>
233 </tr>
234 <tr>
235 <ti>ppc</ti>
236 <ti>G4, G5, power3, power4, power5, ppc, ppc64</ti>
237 <ti>InstallCDs, stages, GRP, Release Notes</ti>
238 <ti>pylon, ranger, dostrow</ti>
239 </tr>
240 <tr>
241 <ti>sparc</ti>
242 <ti>sparc32, sparc64</ti>
243 <ti>InstallCDs, stages, Release Notes</ti>
244 <ti>gustavoz, weeve</ti>
245 </tr>
246 <tr>
247 <ti>x86</ti>
248 <ti>x86, i686</ti>
249 <ti>InstallCD, stages, LiveCD, Release Notes</ti>
250 <ti>agaffney</ti>
251 </tr>
252 </table>
253
254 <p>
255 The following unsupported architectures are tentatively releasing 2008.0:
256 </p>
257
258 <table>
259 <tr>
260 <th>Architecture</th>
261 <th>Subarch(es)</th>
262 <th>Expected Components</th>
263 <th>Release Coordinator(s)</th>
264 </tr>
265 <tr>
266 <ti>ia64</ti>
267 <ti>ia64</ti>
268 <ti>InstallCDs, stages, Release Notes</ti>
269 <ti>plasmaroo</ti>
270 </tr>
271 <tr>
272 <ti>mips</ti>
273 <ti>mips</ti>
274 <ti>LiveCD, stages, netboot images</ti>
275 <ti>Kumba</ti>
276 </tr>
277 </table>
278
279 <p>
280 If information regarding a specific architecture is wrong or has been omitted,
281 please contact the release operations manager.
282 </p>
283
284 </body>
285 </section>
286 -->
287
288 <!-- <section>
289 <title>Release Resources</title>
290 <body>
291
292 <p><b>Release Notes:</b></p>
293
294 <ul>
295 <li><uri link="alpha-release-notes.xml">Alpha Release Notes</uri></li>
296 <li><uri link="amd64-release-notes.xml">AMD64 Release Notes</uri></li>
297 <li><uri link="hppa-release-notes.xml">HPPA Release Notes</uri></li>
298 <li><uri link="ppc-release-notes.xml">PPC Release Notes</uri></li>
299 <li><uri link="sparc-release-notes.xml">SPARC Release Notes</uri></li>
300 <li><uri link="x86-release-notes.xml">x86 Release Notes</uri></li>
301 </ul>
302
303 <p>
304 There will be DIGESTS files for all release media on the Gentoo mirrors.
305 </p>
306
307 <p>
308 All release media will be signed by the <c>Gentoo Linux Release Engineering
309 (releng@g.o)</c> PGP key. The public key ID is <c>0x17072058</c>, and
310 the key is available through the <c>subkeys.pgp.net</c> keyserver.
311 </p>
312
313 </body>
314 </section> -->
315
316 </chapter>
317
318 </guide>
319
320
321
322 --
323 gentoo-commits@l.g.o mailing list