Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
It appears that some users think that adding comments to an update which has been push to stable for weeks is a reasonable way to report an issue. And while I don't want to ignore them, I also don't have a good way to answer them besides adding further spam to a long-closed update.
It would probably be best if we could somehow automatically close a ticket to comments after has been pushed to stable. Perhaps at other times too, such as when an update has been superseded or withdrawn. (Maybe that's already the case; I don't know.) I'm not sure if it is more reasonable to have a cutoff at the exact moment the update is pushed, or to wait a bit, but the former is probably easier to implement.
If it's not reasonable to actually close commenting, would it be possible to display some sort of warning that after updates have been pushed (or superseded or withdrawn) that additional comments will not affect the process and that tickets should be filed in bugzilla instead?