Gentoo Archives: gentoo-project

From: hasufell <hasufell@g.o>
To: gentoo-project@l.g.o
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2013-09-10
Date: Thu, 29 Aug 2013 13:37:34
Message-Id: 521F4E95.1000909@gentoo.org
In Reply to: Re: [gentoo-project] Call for agenda items - Council meeting 2013-09-10 by Rich Freeman
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 On 08/29/2013 01:21 PM, Rich Freeman wrote:
5 > On Wed, Aug 28, 2013 at 10:09 PM, Patrick Lauer
6 > <patrick@g.o> wrote:
7 >> On 08/29/2013 01:02 AM, Ulrich Mueller wrote:
8 >>>>>>>> On Wed, 28 Aug 2013, hasufell wrote:
9 >>>
10 >>>> No, it does not concern a single package only. This is about
11 >>>> making a clear policy. There are more examples of packages
12 >>>> with broken useflags such as app-editors/nano[debug] or other
13 >>>> "vanilla" useflags for glibc and so on which are all in
14 >>>> STABLE branch.
15 >>>
16 >>>> This was already discussed in #gentoo-qa and it seems there
17 >>>> is no clear consensus about the issue. That's where the
18 >>>> council has to make a call.
19 >>>
20 >>> As I said, get a resolution from QA first, before escalating to
21 >>> the council. The procedure for this is clearly outlined in GLEP
22 >>> 48.
23 >>>
24 >> QA policy has always been "if it doesn't compile either fix it or
25 >> mask it"
26 >>
27 >> I don't even see why this needs discussion.
28 >>
29 >> Do not expose users to breakage, OR ELSE (or else someone will
30 >> fix it for you)
31 >
32 > Agree, but if this was discussed in #gentoo-qa and there was no
33 > clear consensus then I suspect that there is more to the issue than
34 > meets the eye. From what was written in the bug comments this
35 > seems like a no-brainer at first glance.
36 >
37 > I think that existing policy and common sense should cover this.
38 > However, if there is some nuance that needs consideration by all
39 > means bring it up.
40 >
41 > What are QA's feelings on the matter?
42 >
43 > Rich
44 >
45
46 The QA lead didn't respond yet, but I tried to raise his attention.
47 -----BEGIN PGP SIGNATURE-----
48 Version: GnuPG v2.0.20 (GNU/Linux)
49 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
50
51 iQEcBAEBAgAGBQJSH06VAAoJEFpvPKfnPDWzu6kH/ioge0WrLmOZoSzRJgusErRQ
52 cbgcKeGCe2BTIJsoC2KfDO6oBHaCdYVkwJBiVFIFaCBk0DchqOjBL0UgmEnwxSYp
53 /8GF29aNuYTETz553vJ6BP7NDLedm9m8t/unTPAPv9JeyD0gg8Gdi4hFfg0y3TOz
54 4HlTd9rQ3KUYjg8U9RNOUN1pLIFtSsV603Vn3GErtsMeeR6vcvDydQg4GfxeSF6T
55 gYQpfkasEAOAb+DjBeB9eryptr4tFjx6Hb+GjPIdC5H6gn8HhhIPYjNYpIrx8QMA
56 CQSWWeefYW4jJkNs/etnjDaNSyI/KLRhIfa0KJ+gy8YgGB795y6kbhijiuw1ypE=
57 =noh0
58 -----END PGP SIGNATURE-----