| 1 |
On Tue, Jan 20, 2004 at 11:42:56PM -0800, Ryan Finnie wrote: |
| 2 |
|
| 3 |
> |
| 4 |
> Sorry, but I'm not feeling the greatest motivation to test ebuilds when |
| 5 |
> reports of "it works!" are met with "we don't care!" If anything, I'd |
| 6 |
> like to see answers to 1) is there a policy for this stuff? and 2) if |
| 7 |
> not, why not? |
| 8 |
> |
| 9 |
|
| 10 |
There is a site (http://gentoo.tamperd.net/stable/index.php) that lets |
| 11 |
us find outdated unstable keywords and mark them stable. |
| 12 |
|
| 13 |
Things in ~arch have to be left there for at least a couple weeks to |
| 14 |
make sure problems don't crop up -- generally, the thing is that we know |
| 15 |
it works if there are no negative bug reports, and so "it works" bug |
| 16 |
reports are only useful on alternate architectures (if you're testing |
| 17 |
stuff on AMD64 that's marked unstable for an extended period of time |
| 18 |
despite being stable on other architectures, a bug report informing us |
| 19 |
of the fact is very handy) |
| 20 |
|
| 21 |
-- |
| 22 |
Jon Portnoy |
| 23 |
avenj/irc.freenode.net |
| 24 |
|
| 25 |
-- |
| 26 |
gentoo-dev@g.o mailing list |
Archives