Originally I thought subscriber lists could be context-sensitive for each bug -- that's why I came up the "explanation of status" field (which has since been driven off into the weeds), for text that would be of interest only to those subscribers in a particular context. But multiple subscriber lists for a bug would be too complicated.
I think we can solve the original problem in two ways:
1. design the interface to discourage derivative distros from recording a bug as needing to be fixed there, if they're not going to do anything special to fix it anyway;
2. let subscribers block types of bugmail globally, such as "Also needs fixing in" messages or "Status changed to something other than closed" messages.
Originally I thought subscriber lists could be context-sensitive for each bug -- that's why I came up the "explanation of status" field (which has since been driven off into the weeds), for text that would be of interest only to those subscribers in a particular context. But multiple subscriber lists for a bug would be too complicated.
I think we can solve the original problem in two ways:
1. design the interface to discourage derivative distros from recording a bug as needing to be fixed there, if they're not going to do anything special to fix it anyway;
2. let subscribers block types of bugmail globally, such as "Also needs fixing in" messages or "Status changed to something other than closed" messages.