Document issue priority
As I was responding to #104 (closed), I realized that it's not written down anywhere how to decide the urgency of an issue. We do time-based releases. We also do ASAP bug fixes. We should document when an issue should be worked on and released ASAP, and when an issue is normal and can go into the next release.
The way I've been thinking about it in my head is that if something is producing invalid source code or otherwise breaking an input file in some way (deleting the file, removing constructs, etc.) that should be fixed ASAP. If something is a stylistic change, but otherwise syntactically valid, there's no rush to get that change out. We should formalize that and add it to the repo.