From: Alec Warner <warnera6@egr.msu.edu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] first council meeting
Date: Sun, 18 Sep 2005 10:05:48 -0400 [thread overview]
Message-ID: <432D743C.7090103@egr.msu.edu> (raw)
In-Reply-To: <20050918130112.GA4041@superlupo.rechner>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Wernfried Haas wrote:
> On Sun, Sep 18, 2005 at 01:32:32PM +0100, Ciaran McCreesh wrote:
>
>>Uhm. That's current policy and has been current policy for several
>>years. No GLEP needed.
>
>
> If that's currenty policy, why does the handbook say something quite
> different then? Does it need to be fixed?
>
> If so, i truly don't understand what ~arch should be about in the
> first place - what use is a ~arch system for testing if everything in
> there just works and stuff to be tested is p.masked?
>
> cheers,
> Wernfried
>
The point being that ~arch is generally for EBUILD testing, not package
testing. This is bad because some PACKAGES need lots of testing but
don't get it because they are in p.mask ( because the PACKAGE is not
stable ). Some people have begun putting unstable PACKAGES in ~arch,
instead of in p.mask because p.mask does not get enough testing done, so
things rot in p.mask forever. For larger packages ( apache, mysql,
gnome ) this system works fine because upstream does a lot of testing.
Since users shy away from p.mask ( things in there can have security
issues for example ) a new PACKAGE testing area was proposed. Packages
in this area would need PACKAGE testing. Users would know that packages
with security issues would not be in this new testing area.
Personally I like Ciaran's wording of the levels.
~arch - Canidate for Stable on Arch
arch - Stable on Arch
You wouldn't suggest a program you hadn't tested as a Canidate for
Stable. That would be utterly retarded. You've tested it
thoroughly(sp?) and it seems to work well for you. You have had other
developers in your herd test it and they also encounter no problems.
Thus it enters ~arch because you cannot find anything wrong with the
package and you think it's stable. If the users find a huge bug you can
regress the ~arch back to the testing layer ( be it p.mask or something
new ) and fix the bug. If no one files a bug for 30 days have an AT
test it and then mark it stable.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQy10O2zglR5RwbyYAQLBcQ/9FPBNN6N2GmGvBpT1T2fnSnPTPiyFais5
4nSedhgi2uwROlCIOCdZevVEGLQbomwuOklWjjHhZK5TRYAmiqnqlSEscn881L10
KqRxTj7ctpBC7WExxvjpCOto4WYos+7jIe9n3mCXCeptv4R4/WBGTIXeHFqij8Mq
ii7tL2fxKR1iCzPJ2Hf596Ip6FeMcL5HPpiZ9TEBrx4Bl47OH42USMKVHUODDV4G
dDlGQKPuItubFsv8D4GwEIEFxWCxbIDj5gvTk3Y3g9gVc07sbFNzcO3RJKaN8zff
msDGONSWXZ4dNuYbPwrIs8IC9VWEctVmHxy3iB/HzIlnAoRIq5+an3QDuy93JlCN
TFmyWhf6MGkR4fovjo+zZ4FC4vGy8jYRuptRZpx2VLSX8fH4ishkZ/dJLOyZsRKC
5irvdz7l9y8q5Ge4ZEd/EkdOaYOAK7ZqxsbydKEImoYwY6yLRwnj+LbG3BO9ukUF
5jxyec+X1wWANaxwiWKZ2+WzXpt/QZUQo+r7tLNKUMOs9MZXIX5yTaaEqSNvCGhf
QHTlRjKOX9Z1YxD2u/mhv9UNYmX/gb9LUz/q9rzVUjHXm7CFB4aQiyGhL+HgEqrW
0h/OCHyShYOzG418Dc1lrJff5vVz5O0u5caIhEzn5Z6iHr0EInaqzr0DCtoFUCKa
uzurfVUN5lQ=
=GI+1
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-18 14:08 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 20:51 [gentoo-dev] first council meeting Aron Griffis
2005-09-15 21:25 ` Olivier Crete
2005-09-15 21:57 ` Chris Gianelloni
2005-09-15 22:20 ` Mike Frysinger
2005-09-16 17:42 ` Paul de Vrieze
2005-09-16 18:14 ` Martin Schlemmer
2005-09-16 18:18 ` Brian Harring
2005-09-16 18:19 ` Simon Stelling
2005-09-16 18:38 ` Ciaran McCreesh
2005-09-16 18:48 ` Paul de Vrieze
2005-09-16 19:00 ` Daniel Ostrow
2005-09-17 9:28 ` Kevin F. Quinn
2005-09-17 9:34 ` Brian Harring
2005-09-17 12:02 ` Kevin F. Quinn
2005-09-17 20:17 ` Mike Frysinger
2005-09-17 21:59 ` Alec Warner
2005-09-17 22:45 ` Mike Frysinger
2005-09-18 6:46 ` Wernfried Haas
2005-09-18 6:51 ` Wernfried Haas
2005-09-18 12:32 ` Ciaran McCreesh
2005-09-18 13:01 ` Wernfried Haas
2005-09-18 14:05 ` Alec Warner [this message]
2005-09-19 1:58 ` Philip Webb
2005-09-18 15:38 ` Ciaran McCreesh
2005-09-18 12:40 ` Matti Bickel
2005-09-26 4:01 ` Andrew Muraco
2005-09-26 4:15 ` Mike Frysinger
2005-09-28 2:53 ` Marius Mauch
2005-09-16 19:02 ` Ciaran McCreesh
2005-09-16 19:12 ` Simon Stelling
2005-09-16 19:34 ` Ciaran McCreesh
2005-09-16 20:46 ` Simon Stelling
2005-09-16 19:15 ` Mike Frysinger
2005-09-16 19:34 ` Ciaran McCreesh
2005-09-16 20:11 ` Paul de Vrieze
2005-09-16 20:21 ` Aron Griffis
2005-09-16 20:25 ` Daniel Ostrow
2005-09-16 20:43 ` Mike Frysinger
2005-09-16 21:50 ` Mike Frysinger
2005-09-16 22:00 ` Kito
2005-09-16 22:23 ` Maurice van der Pot
2005-09-16 22:45 ` Carsten Lohrke
2005-09-16 23:14 ` Mike Frysinger
2005-09-16 20:37 ` Olivier Crete
2005-09-16 20:17 ` Carsten Lohrke
2005-09-16 20:38 ` Ciaran McCreesh
2005-09-16 21:23 ` Carsten Lohrke
2005-09-16 21:34 ` Ciaran McCreesh
2005-09-16 21:41 ` Patrick Lauer
2005-09-16 21:46 ` Ciaran McCreesh
2005-09-16 22:43 ` Carsten Lohrke
2005-09-16 23:00 ` Ciaran McCreesh
2005-09-16 23:19 ` Carsten Lohrke
2005-09-16 20:33 ` Mike Frysinger
2005-09-16 20:44 ` Ciaran McCreesh
2005-09-16 20:59 ` Mike Frysinger
2005-09-16 21:10 ` Ciaran McCreesh
2005-09-16 21:20 ` Simon Stelling
2005-09-16 21:26 ` Ciaran McCreesh
2005-09-16 21:51 ` Mike Frysinger
2005-09-19 9:32 ` Paul de Vrieze
2005-09-16 22:48 ` Carsten Lohrke
2005-09-16 21:57 ` Martin Schlemmer
2005-09-16 22:17 ` Mike Frysinger
2005-09-24 13:44 ` [gentoo-dev] " Duncan
2005-09-16 22:51 ` [gentoo-dev] " Carsten Lohrke
2005-09-16 20:16 ` Aron Griffis
2005-09-17 6:39 ` Elfyn McBratney
2005-09-15 23:47 ` Jason Stubbs
2005-09-24 13:21 ` [gentoo-dev] " Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=432D743C.7090103@egr.msu.edu \
--to=warnera6@egr.msu.edu \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox