The text in https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29 is a recent incantation based on what I’ve been using for the past year or so.
What that page doesn’t yet mention is that sometimes we do jump straight to Invalid instead of Incomplete. Sometimes it’s out of necessity (the bug has too many attributes to qualify for automatic expiry), and sometimes it’s just out of frustration/impatience. This has turned out to be quite uncontroversial, with only around one in every few hundred bug reporters complaining. And when people do complain it’s usually about the fact that you commented at all, and not a valid complaint: “it’s been 10 years, thanks for nothing”.
My personal rule of thumb is to use Invalid if:
- There is no obvious evidence the bug is still valid; and
- The Ubuntu release is past EOL by more than one cycle.
Using Invalid in this case should be no cause for concern. In the rare case when a bug does come back to life it’s a trivial status change.
Having done this for thousands of bugs so far I am no longer afraid of using Invalid in some cases, in place of Incomplete.