On Fri, 2 Aug 2024, 00:29 Sam James via Gcc, <gcc@gcc.gnu.org> wrote:
> Hi! > > This came out of some discussion with Arsen and prompted by some other > comments on IRC. > > At the moment, during release time, maintainer-scripts/branch_changer.py > is run by release managers and causes a large amount of bugmail to be > sent both to CCs/assignees but also to the gcc-bugs ML. The activity > comes from the RM's personal account. In the past, I've missed real > activity on bugs (including a question to me) as well as some other > email drowned out in the notification emails. > > What do people think about possibly having a special 'GCC releases' > account which only the RMs have an API key to, possibly suppresses > sending email to begin with, and is ignored by gcc-bugs? It would allow > easier filtering out of the mail. > I don't care which account does the changes but I'd prefer to keep the emails. There's always at least one that reminds me a bug is actually fixed and should be closed, or the target milestone should be removed because it isn't going to be fixed on that branch now. If they were just sent from a separate account then I'd still get emails but you could filter them out more easily. > (I'm familiar enough with BZ to say it should be trivially doable, with > the exception of suppressing *sending* the mail to begin with, which I'd > have to investigate.) > > thanks, > sam >
