Gentoo Archives: gentoo-commits

From: "Donnie Berkholz (dberkholz)" <dberkholz@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] gentoo commit in xml/htdocs/news: 20080123_releng_beta.xml
Date: Thu, 24 Jan 2008 08:21:36
Message-Id: E1JHxL3-0001Qe-Iu@stork.gentoo.org
1 dberkholz 08/01/24 08:21:33
2
3 Added: 20080123_releng_beta.xml
4 Log:
5 Add news about plans for a public beta for 2008.0.
6
7 Revision Changes Path
8 1.1 xml/htdocs/news/20080123_releng_beta.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/news/20080123_releng_beta.xml?rev=1.1&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/news/20080123_releng_beta.xml?rev=1.1&content-type=text/plain
12
13 Index: 20080123_releng_beta.xml
14 ===================================================================
15 <?xml version="1.0" encoding="utf-8"?>
16
17 <!DOCTYPE news SYSTEM "/dtd/guide.dtd">
18
19 <news gentoo="yes" category="main">
20 <poster>dberkholz</poster>
21 <date>2008-01-23</date>
22 <title>Public beta release planned for 2008.0 release cycle</title>
23 <body>
24
25 <table>
26 <tr>
27 <th colspan="2">Tentative schedule (dates may change):</th>
28 </tr>
29 <tr>
30 <ti>Feb. 1</ti>
31 <ti>Snapshot of the tree taken</ti>
32 </tr>
33 <tr>
34 <ti>Feb. 25</ti>
35 <ti>Docs due to GDP from release coordinators</ti>
36 </tr>
37 <tr>
38 <ti>Feb. 25</ti>
39 <ti>Snapshot frozen for beta</ti>
40 </tr>
41 <tr>
42 <ti>Feb. 29</ti>
43 <ti>Docs finalized</ti>
44 </tr>
45 <tr>
46 <ti>Mar. 3</ti>
47 <ti>Beta1 released</ti>
48 </tr>
49 <tr>
50 <ti>Mar. 14</ti>
51 <ti>Final upload</ti>
52 </tr>
53 <tr>
54 <ti>Mar. 17</ti>
55 <ti>Release</ti>
56 </tr>
57 </table>
58
59
60 <p>
61 Public beta releases play a major role in the <uri
62 link="http://www.gentoo.org/proj/en/releng/">Release Engineering
63 team's</uri> revamped plans for 2008.0. Releng lead <mail
64 link="wolf31o2">Chris Gianelloni</mail> said he hoped beta releases would
65 increase community participation as well as the quality of the final
66 release. These feature-complete public betas will require the earlier
67 development of release materials, another component of the 2008.0
68 changes. To ensure sufficient time for beta testing, a mandatory 2-week
69 testing period will follow the beta release.
70 </p>
71
72 <p>
73 A comprehensive testing checklist will be developed on the <uri
74 link="http://archives.gentoo.org/gentoo-releng/">gentoo-releng mailing
75 list</uri>, as will a list of which details of testers' machines and
76 environments they should turn in to developers. In the past, testers often
77 provided insufficient information to releng developers because of vague
78 instructions. Now, a new form will include all of the required questions
79 and details. "Sadly you almost want a beta that phones home as to what it
80 was successfully run on," said <mail link="tgall">Tom Gall</mail>. <mail
81 link="opfer">Christian Faulhammer</mail> suggested using a hardware
82 reporting tool such as <uri
83 link="http://packages.gentoo.org/package/app-admin/hwreport">app-admin/hwreport</uri>.
84 </p>
85
86 <p>
87 More news on the 2008.0 release will appear over the next few days.
88 </p>
89 </body>
90 </news>
91
92
93
94 --
95 gentoo-commits@l.g.o mailing list