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:31:27
Message-Id: E1JHsoG-0008Av-6y@stork.gentoo.org
1 wolf31o2 08/01/24 03:31:24
2
3 Modified: index.xml
4 Log:
5 Spell out Public Relations and remove the Not Completed from the status boxes.
6
7 Revision Changes Path
8 1.2 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.2&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/releng/release/2008.0/index.xml?rev=1.2&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/releng/release/2008.0/index.xml?r1=1.1&r2=1.2
13
14 Index: index.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/releng/release/2008.0/index.xml,v
17 retrieving revision 1.1
18 retrieving revision 1.2
19 diff -u -r1.1 -r1.2
20 --- index.xml 24 Jan 2008 03:28:13 -0000 1.1
21 +++ index.xml 24 Jan 2008 03:31:23 -0000 1.2
22 @@ -30,7 +30,7 @@
23 <li>Release Operations: <mail>wolf31o2</mail></li>
24 <li>Documentation: <mail>nightmorph</mail></li>
25 <li>Infrastructure: <mail>robbat2</mail></li>
26 -<li>PR: <mail>dberkholz</mail></li>
27 +<li>Public Relations: <mail>dberkholz</mail></li>
28 <li>Security: <mail>wolf31o2</mail></li>
29 </ul>
30
31 @@ -74,7 +74,7 @@
32 After this point, packages are added/updated in the snapshot only if it is
33 necessary due to the potential impact of the issue, such as security bugs, or
34 release-specific changes, such as an updated livecd-tools.</ti>
35 -<ti>Not Completed</ti>
36 +<ti></ti>
37 </tr>
38 <tr>
39 <ti>QA builds/testing</ti>
40 @@ -82,7 +82,7 @@
41 <ti>Several builds of the release media are made on each architecture, with
42 modifications being made to the snapshot and the release building tools, as
43 necessary.</ti>
44 -<ti>Not Completed</ti>
45 +<ti></ti>
46 </tr>
47 <tr>
48 <ti>Doc updates</ti>
49 @@ -91,21 +91,21 @@
50 by this date for the upcoming release. Things that are commonly updated are the
51 kernel versions used, kernel command line options that have been added/removed,
52 and changes to the installation process.</ti>
53 -<ti>Not Completed</ti>
54 +<ti></ti>
55 </tr>
56 <tr>
57 <ti>Snapshot freeze (BETA)</ti>
58 <ti>25 Feb 2008</ti>
59 <ti>The snapshot is frozen to build an initial BETA release for wider testing
60 in the community. Once the BETA is released, the snapshot is unfrozen.</ti>
61 -<ti>Not Completed</ti>
62 +<ti></ti>
63 </tr>
64 <tr>
65 <ti>Handbook updated</ti>
66 <ti>29 Feb 2008</ti>
67 <ti>The updated Handbook tarballs for each architecture are due to be delivered
68 to Release Engineering for use on the BETA release.</ti>
69 -<ti>Not Completed</ti>
70 +<ti></ti>
71 </tr>
72 <tr>
73 <ti>BETA information</ti>
74 @@ -113,28 +113,28 @@
75 <ti>The press release/news item for the BETA release is written and has been
76 submitted to Release Engineering for approval. The BETA checklist is completed
77 and ready for distribution.</ti>
78 -<ti>Not Completed</ti>
79 +<ti></ti>
80 </tr>
81 <tr>
82 <ti>BETA upload</ti>
83 <ti>2 Mar 2008</ti>
84 <ti>The BETA is uploaded to the release staging server for distribution under
85 the experimental directory on participating mirrors.</ti>
86 -<ti>Not Completed</ti>
87 +<ti></ti>
88 </tr>
89 <tr>
90 <ti>BETA release</ti>
91 <ti>3 Mar 2008</ti>
92 <ti>The BETA is publicly released. The front page is updated to reflect this and
93 notification is sent to news outlets.</ti>
94 -<ti>Not Completed</ti>
95 +<ti></ti>
96 </tr>
97 <tr>
98 <ti>Snapshot freeze (Final)</ti>
99 <ti>10 Mar 2008</ti>
100 <ti>This is the due date for the final snapshot. After this point, no updates
101 are made to the snapshot and the final build phase begins.</ti>
102 -<ti>Not Completed</ti>
103 +<ti></ti>
104 </tr>
105 <tr>
106 <ti>Doc updates</ti>
107 @@ -142,42 +142,42 @@
108 <ti>Any additional changes to the Handbook must be submitted by this date. This
109 conicides with the snapshot freeze, so no changes will happen in the snapshot
110 post this date to ensure the accuracy of the Handbook.</ti>
111 -<ti>Not Completed</ti>
112 +<ti></ti>
113 </tr>
114 <tr>
115 <ti>Handbook updated</ti>
116 <ti>12 Mar 2008</ti>
117 <ti>The updated Handbook tarballs for each architecture are due to be delivered
118 to Release Engineering for use on the final release.</ti>
119 -<ti>Not Completed</ti>
120 +<ti></ti>
121 </tr>
122 <tr>
123 <ti>Media uploaded</ti>
124 <ti>15 Mar 2008</ti>
125 <ti>All release media is uploaded to the release staging server (poseidon) by
126 this date to be prepared for release.</ti>
127 -<ti>Not Completed</ti>
128 +<ti></ti>
129 </tr>
130 <tr>
131 <ti>Final preparation</ti>
132 <ti>16 Mar 2008</ti>
133 <ti>One final check is made of all release materials, DIGESTS files are signed,
134 and any additional tasks are completed.</ti>
135 -<ti>Not Completed</ti>
136 +<ti></ti>
137 </tr>
138 <tr>
139 <ti>Release handover</ti>
140 <ti>16 Mar 2008</ti>
141 <ti>Release Engineering makes one final check of all materials, then hands it
142 over to Infrastructure for staging and release.</ti>
143 -<ti>Not Completed</ti>
144 +<ti></ti>
145 </tr>
146 <tr>
147 <ti>Release</ti>
148 <ti>17 Mar 2008</ti>
149 <ti>All news items are committed, the release materials and Handbook are made
150 visible to the public, and Release Engineering takes a well-deserved break.</ti>
151 -<ti>Not Completed</ti>
152 +<ti></ti>
153 </tr>
154 </table>
155
156
157
158
159 --
160 gentoo-commits@l.g.o mailing list