------- Comment #13 from joseph at codesourcery dot com 2010-02-10 00:20 ------- Subject: Re: Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.4.5
The main email-related functionality for GCC is: all bugs in the "gcc" product automatically get CC:ed to gcc-bugs@gcc.gnu.org (maybe other lists depending on the component, or for other products). Email replies get body and attachments automatically entered in the relevant bug, with an account created for the sender if they didn't already have one. If you preserve that, most of the important email handling functionality is there. There is I think some mechanism for other bug manipulations by email, but I don't think many people (if any at all) use it. contrib/regress-submit.pl might once have been used for automatic bug submissions by regression testers, but there hasn't been such submission for years, so I think it can be ignored. User accounts with email addresses @gcc.gnu.org automatically get some extra privileges. I don't know where this is configured. As noted, we can reasonably kill gccbug and so ignore anything related to GNATS. As discussed, there are various new fields added to GCC Bugzilla - while some of the standard Bugzilla fields are removed as inapplicable (build / host / target is the proper way of describing the platform where a GCC bug is observed). There are also some changes to the set of states a bug can be in. Hopefully the conclusion will be that we don't need GCC-specific scripts in contrib/ but can preserve the various GCC-specific logic (possibly implemented in a better way using newer 3.4 infrastructure). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011
