-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, 20 May 2005, Duncan Coutts wrote:
Sorry folks this was my fault. I've sent my grovelling apology to the sparc team. Hopefully they'll accept my apologies and put my digressions down to me being a new dev. :-)
You can only take some of the credit Duncan, but not all of it :)
Every once and a while it seems a reminder such as this is needed as people tend to start playing with package keywords when they shouldn't be. It's kind of like guarding the cookie jar, you can't ever let your guard down, even if you cut off everyone else's hands. I try not to point fingers or name names since it's not something I like done to myself. I'd also like to think that this gives such guilty parties a better understanding of why the arch teams (and especially SPARC) can be so maniacal about this sometimes, in hopes that it will lessen and/or prevent this problem in the future.
From my perspective, if a package maintainer asks for testing and theability to keyword (i.e. Spanky asking me if it was OK to bump binutils to 2.16, to which I said yes) then that is fine. However adding or changing keywords in an ebuild for which you cannot test (regardless of how trivial the changes are or how "portable" the programming language of said package is supposed to be) is really where I'm looking at here.
For some odd reason, trying to ensure QA (even in the nicest of fashions) seems to result in a majority of less than positive responses. Even recently I've had a developer get quite confrontational with me over email when I nicely asked him not to stabilize packages for which he could not test (even if the changes were supposedly trivial). History has shown that we cannot depend on assuming that trivial changes for me == works for you if we want to have some level of Q in QA.
Cheers,
- -- Jason Wever
Gentoo/Sparc Co-Team Lead
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCjkP3dKvgdVioq28RAqw+AJ9yuqHTVZSsdnfyFt9PgJSm3jt+2QCdEjwE TS+flVWEr60GwuMEdWIqV/g= =xrIF -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list
