On 9 January 2013 18:17, Vicente Olivert Riera <per...@carrosses.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello everyone :-) > > some devs and I were talking about the fact that TESTED bugzilla > keyword may need a change on his description, or, maybe it's needed to > create new TESTED_${ARCH} keywords. > > Personally, I was using TESTED keyword when an ebuild was tested on > every CC'ed arch, but there are some discrepancy about that, so we > decided to discuss this topic on gentoo-dev@ > > What do you think? What about to create a TESTED_${ARCH} keyword for > every arch? > > Best regards, > - -- > ************************* > Vicente Olivert Riera > per...@carrosses.com > ID GnuPG: 5AE9E7B2E9BBCBA8 > ************************* > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAlDtmAIACgkQWunnsum7y6i1GQCdE60IS5OjVYjBn6y9YFU5QhhC > hKsAn3mPVPclED+CP8db+inhhQmfFaAT > =W+jm > -----END PGP SIGNATURE----- >
The "Keywords" field will end up huge if every CC'd arch uses it's own TESTED_$ARCH keyword. Although only x86 and amd64 have arch testers nowadays. Would it be preferred to have a list of checkboxes for every CC'd arch, and Arch Testers have privileges to select them if a package works for their arch? This would eliminate the "works on $arch" comments that flood the stabilization bugs. -- Regards, Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2