Steve Langasek <vorlon@netexpress.net> writes: > So where does that leave us? If none of the people who are in a > position to approve packages for inclusion in testing or > testing-security are willing to commit resources to doing so, it seems > the only other option that could have an effect is to submit a patch to > the website, to add a skull and crossbones everywhere that testing is > mentioned. Disclaimer: I'm just a lowly user. If testing is just a release tool that isn't supposed to be used until a freeze, why is it being offered up for use? Wouldn't it be better all around (disk space on mirrors, support questions about testing, rooted boxes, threads like this, and such) to have the testing scripts work on a private pool on some debian machine somewhere and not mirrored out to the world? Another question: does Debian provide to developers access to machines on all 11 arches for building packages? -- Kevin
Attachment:
pgpzsUZfSPqdn.pgp
Description: PGP signature