[gentoo-dev] Email Overload; Make summaries and bugs for test requests

[Jason Wever <weeve@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

Hi All,

Since our -dev mailing list is now receiving an enormous amount of
traffic each day, I'd like to suggest bringing/bring back up the summaries
idea previously mentioned a few months ago.  Due to the fact that we all
have limited time to work on Gentoo, and we can't spend all of it reading
the 50+ emails on -dev every day (not to mention other list(s) we may be
on).. So please, if a thread ends up resulting in something devs need to
read(i.e. policy changes), please make a summary email.

Also, for sparc, if you want us to test something, it is *HIGHLY
SUGGESTED* that you make a bug for it and CC the sparc team on it
<sparc@gentoo.org>. As I've mentioned in the above paragraph about email
overload, it's easy for your test request to get lost in the shuffle
(especially if it's at the top of the 50+ emails to read).  This will
guarantee the best response from the team.  If you want to do whatever
with your ebuild(s) in the test request by a certain date, please indicate
that in the bug.  

Thanks,
-- 
Jason Wever
Gentoo/Sparc Team Lead

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]