Gentoo Archives: gentoo-dev

From: Danny van Dyk <kugelfang@g.o>
To: gentoo-dev@l.g.o, jakub@g.o
Subject: [gentoo-dev] Policies (was: [RFC] QA Team's role)
Date: Tue, 28 Feb 2006 16:40:32
Message-Id: 44047935.2050901@gentoo.org
In Reply to: Re[2]: [gentoo-dev] [RFC] QA Team's role by Jakub Moc
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 Hi Jakub,
5
6 Jakub Moc schrieb:
7 | 28.2.2006, 16:29:07, Stephen Bennett wrote:
8 |>>When and where has been the following change discussed and who
9 |>>approved that?
10 |>>
11 |>>http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/proj/en/devrel/handbook/hb-guide-ebuild.xml?r1=1.25&r2=1.26&root=gentoo
12 |>According to my recollection, it was discussed between members of QA
13 |>and devrel. According to the CVS logs, it was committed by a member of
14 |>devrel, at QA's request. You can't pass it off as a QA project
15 |>conspiracy, since they didn't make the change.
16 | I'm sorry, but discussing such stuff affecting pretty much everyone who
17 | writes ebuilds among a couple of people simply isn't enough to make this a
18 | policy. And then silently applying this and starting to scream "QA
19 | violation, look, what a nasty QA violation!!!" is plain ridiculous.
20 Well, it was common sense before. Especially because it was part of the
21 devmanual. I know, the next argument will be: The devmanual is not
22 official. However, this particular text had been part of the devmanual
23 for a long time. Many devs read it and afaict nobody objected against it
24 while it was 'unofficial'. In my opinion, there was enough time to raise
25 a hand and yell: 'I don't like it'.
26
27 Beside this, I'd like to support the non-interactive mode on the base of
28 efficiency: It is better to install a package with a default and sane
29 set of USE flags instead of breaking the whole update process.
30
31 However, this incident should be logged by portage.
32
33 | Punting every single piece of broken sh*t from the tree requires notifying
34 | everyone on -dev ml and allowing a period of time before it's actually
35 done,
36 | so silently changing/stating policies is a very broken practice.
37 Nobody changed anything. It was written down before in the devmanual and
38 then incorporated into the developer handbook.
39
40 If you don't agree with the contents, why didn't you raise your
41 opposition earlier?
42
43 If you agree with the contents, please ask yourself if the current
44 discussion is necessary.
45
46 I'm looking forward to your answers on the last 2 points.
47 Danny
48 - --
49 Danny van Dyk <kugelfang@g.o>
50 Gentoo/AMD64 Project, Gentoo Scientific Project
51 -----BEGIN PGP SIGNATURE-----
52 Version: GnuPG v1.4.2 (GNU/Linux)
53
54 iD8DBQFEBHk1aVNL8NrtU6IRAlRbAKCH233GWmOQWlRy/DQQh/aRR++4ZACfd230
55 rYQgmnvH9Y/0YSijnCSAOIc=
56 =QQEa
57 -----END PGP SIGNATURE-----
58 --
59 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] Policies (was: [RFC] QA Team's role) Jakub Moc <jakub@g.o>