-----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

Reply via email to