| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Wernfried Haas wrote: |
| 5 |
> On Sun, Sep 18, 2005 at 01:32:32PM +0100, Ciaran McCreesh wrote: |
| 6 |
> |
| 7 |
>>Uhm. That's current policy and has been current policy for several |
| 8 |
>>years. No GLEP needed. |
| 9 |
> |
| 10 |
> |
| 11 |
> If that's currenty policy, why does the handbook say something quite |
| 12 |
> different then? Does it need to be fixed? |
| 13 |
> |
| 14 |
> If so, i truly don't understand what ~arch should be about in the |
| 15 |
> first place - what use is a ~arch system for testing if everything in |
| 16 |
> there just works and stuff to be tested is p.masked? |
| 17 |
> |
| 18 |
> cheers, |
| 19 |
> Wernfried |
| 20 |
> |
| 21 |
|
| 22 |
The point being that ~arch is generally for EBUILD testing, not package |
| 23 |
testing. This is bad because some PACKAGES need lots of testing but |
| 24 |
don't get it because they are in p.mask ( because the PACKAGE is not |
| 25 |
stable ). Some people have begun putting unstable PACKAGES in ~arch, |
| 26 |
instead of in p.mask because p.mask does not get enough testing done, so |
| 27 |
things rot in p.mask forever. For larger packages ( apache, mysql, |
| 28 |
gnome ) this system works fine because upstream does a lot of testing. |
| 29 |
|
| 30 |
Since users shy away from p.mask ( things in there can have security |
| 31 |
issues for example ) a new PACKAGE testing area was proposed. Packages |
| 32 |
in this area would need PACKAGE testing. Users would know that packages |
| 33 |
with security issues would not be in this new testing area. |
| 34 |
|
| 35 |
Personally I like Ciaran's wording of the levels. |
| 36 |
|
| 37 |
~arch - Canidate for Stable on Arch |
| 38 |
arch - Stable on Arch |
| 39 |
|
| 40 |
You wouldn't suggest a program you hadn't tested as a Canidate for |
| 41 |
Stable. That would be utterly retarded. You've tested it |
| 42 |
thoroughly(sp?) and it seems to work well for you. You have had other |
| 43 |
developers in your herd test it and they also encounter no problems. |
| 44 |
Thus it enters ~arch because you cannot find anything wrong with the |
| 45 |
package and you think it's stable. If the users find a huge bug you can |
| 46 |
regress the ~arch back to the testing layer ( be it p.mask or something |
| 47 |
new ) and fix the bug. If no one files a bug for 30 days have an AT |
| 48 |
test it and then mark it stable. |
| 49 |
|
| 50 |
-----BEGIN PGP SIGNATURE----- |
| 51 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 52 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
| 53 |
|
| 54 |
iQIVAwUBQy10O2zglR5RwbyYAQLBcQ/9FPBNN6N2GmGvBpT1T2fnSnPTPiyFais5 |
| 55 |
4nSedhgi2uwROlCIOCdZevVEGLQbomwuOklWjjHhZK5TRYAmiqnqlSEscn881L10 |
| 56 |
KqRxTj7ctpBC7WExxvjpCOto4WYos+7jIe9n3mCXCeptv4R4/WBGTIXeHFqij8Mq |
| 57 |
ii7tL2fxKR1iCzPJ2Hf596Ip6FeMcL5HPpiZ9TEBrx4Bl47OH42USMKVHUODDV4G |
| 58 |
dDlGQKPuItubFsv8D4GwEIEFxWCxbIDj5gvTk3Y3g9gVc07sbFNzcO3RJKaN8zff |
| 59 |
msDGONSWXZ4dNuYbPwrIs8IC9VWEctVmHxy3iB/HzIlnAoRIq5+an3QDuy93JlCN |
| 60 |
TFmyWhf6MGkR4fovjo+zZ4FC4vGy8jYRuptRZpx2VLSX8fH4ishkZ/dJLOyZsRKC |
| 61 |
5irvdz7l9y8q5Ge4ZEd/EkdOaYOAK7ZqxsbydKEImoYwY6yLRwnj+LbG3BO9ukUF |
| 62 |
5jxyec+X1wWANaxwiWKZ2+WzXpt/QZUQo+r7tLNKUMOs9MZXIX5yTaaEqSNvCGhf |
| 63 |
QHTlRjKOX9Z1YxD2u/mhv9UNYmX/gb9LUz/q9rzVUjHXm7CFB4aQiyGhL+HgEqrW |
| 64 |
0h/OCHyShYOzG418Dc1lrJff5vVz5O0u5caIhEzn5Z6iHr0EInaqzr0DCtoFUCKa |
| 65 |
uzurfVUN5lQ= |
| 66 |
=GI+1 |
| 67 |
-----END PGP SIGNATURE----- |
| 68 |
-- |
| 69 |
gentoo-dev@g.o mailing list |
Archives