[gentoo-dev] Re: RFC: AT emerge info cruft > attachments on bugs.g.o

Tach Jeroen,                                  0x2B859DE3 (PGP-PK-ID)

Jeroen Roovers schrieb:
> Inlining emerge info in comments bloats the e-mail message to roughly
> 2.5 times the normal size. I could have spoken out to get AT comments
> banned altogether or to urge arches with AT teams to find a proper
> technical solution to communicate outside of bugs.g.o. I think using
> attachments instead of inlining is a pretty good temporary solution to a
> communication problem that has for now been solved by making every
> stabilisation bug report a dumping ground for a ton of information that
> becomes obsolete within a few days.

 Basically you are right about "cruft", but the information the ATs submit  
should be accessible to everyone so the actual solution without  
attachments (because of more work) is the bestTM.  What other ways of  
communication between ATs and devs do you propose?  Some kind of arch  
Bugzilla? IMO it should be permanent with a link from the stabilisation  
bug so that everyone (devs, users, ATs) can follow the path of  
stabilisation.



V-Li

-- 
Fingerprint: 68C5 D381 B69A A777 6A91 E999 350A AD7C 2B85 9DE3
http://www.gnupg.org/