Every time I change a bug from "Individual Port(s)" component to "Ports Framework" component, bugzilla adds freebsd-ports-bugs in cc: This is wrong.
Antoine, can you help me understand in what sense you consider it wrong? The current configuration of the Ports Framework component ism as you correctly observe: Default Assignee: portmgr@ Default CC: freebsd-ports-bugs@ I believe it was configured in this manner to ensure that *all* newly created issues are visible to the mailing list and the community, and that these issues aren't special in the sense that they are as valuable for anyone to contribute to (if patches might be required) as other issues in other components. Why shouldn't portmgr@ (or for that matter, any !individual port issues) be CC'd to the lists? I also noticed while looking at the component configuration, that "Package Infrastructure" component issues are not CC'd to the list, though they should have been.
In my opinion it doesn't provide any added value to cc: freebsd-ports-bugs. It only makes sense as assignee for not yet triaged stuff. If you fear that some changes may be missed by the maintainer of the component, it would be better to have the auto-assigner doing things better. For instance, for bug #201193, bz did: Assignee: portmgr@ CC: freebsd-ports-bugs@ In my opinion it should do: Assignee: ale@ CC: portmgr@ (Mk/bsd.php.mk:38:PHP_Include_MAINTAINER= ale@FreeBSD.org) for bug #200997, it did: Assignee: portmgr@ CC: freebsd-ports-bugs@ Submitter added CC: acm@ manually In my opinion it should do: Assignee: acm@ CC: portmgr@ (Mk/bsd.fpc.mk:36:FPC_Include_MAINTAINER= acm@FreeBSD.org) I doubt ale@ and acm@ are subscribed to freebsd-ports-bugs@ so adding it in CC: doesn't help.