Follow up on #6050:

First of all, thanks for the fast response to #6050 and owning up to the mistake. It's unfortunately rare for someone to step up and say "I messed up" these. I've been an iTerm user for years and really appreciate the work that goes into keeping the project moving forward, so I hope this situation hasn't made you want to quit.

Now that the problem is fixed, I think it would be worthwhile to do a post-mortem. My hope is that this will benefit both the iTerm project and other projects whose maintainers are keeping an eye on this situation. dnslookupissue on the wiki begins this process.

A few questions I think are worth addressing:

1. Why did #3688 (closed) and #5303 (closed) go unnoticed by the community? Both issues were addressed but didn't blow up the way this one did.
2. What steps can be taken to make sure this (or similarly significant issues) doesn't happen in the future?
3. What can the community do to help when something like this does happen? I've heard a lot of yelling about how we should all uninstall iTerm, but that's just silly and not helpful. What else can we do?