I started getting many emails from bugzilla regarding retirement procedures (as I am on forum@ alias). Although I understand that it is necessary to document and proceed with retirements, logging activities from the retirement script to bugzilla led to a flood on my email account that I do not think it is desired nor required. I suggest that the script should submit a single entry with all its procedures, once. Reproducible: Always
This is due to the distributed design of the scripts. They run independently on different hosts, and report their results to the bugs. If we were to change that, we would have to introduce a central scheduler that would wait for all results and publish them -- or publish them manually from mails. I don't think the former is worth the effort, and that the gain outweighs the extra effort with the latter. Please note that for the first bugs there have been a few extra comments due to accidental duplication of cronjob. This has been fixed, and so right now we expect 3 or 4 comments per retirement. Plus, we really don't expect the retirements to be this common, especially with no new recruits. I'd rather consider this a single incident where a large batch of long-unprocessed retirements were finally handled. Hopefully, from now on retirements will be handled without delays and will not pile up. Finally, you can just handle your part of the work early and un-CC yourself. That's what planet does. It's not like Infra is in a hurry to start the automated procedures.
Thanks for the explanation. Although I am still not agreeing with the design principle of using Bugzilla as a logger for this script, I understand the costs involved in rewriting it and how this was a peculiar situation for starters. Besides, I could make the case to keep forums etc in the forwarders of a retirement bug for the case where the developer comes back. Closing the bug as WONTFIX, as it seems to be the case.
