From both sides
There is a lot of finger pointing in the comments, it seems the article struck a nerve.
The most important thing for a developer is to not get emotionally involved in the code or product. Its just a product, just a job. When someone complains in some way it is usually for a good reason. Not always a reason which you are to blame for, that is true.
The point is to meet every new customer who has a complaint with an open mind. Assume that the person is a person who isn't dumber or in any way inferior to you. Instead as a person who has different experiences and thus can't be expected to know what you know.
(Someone talked about code forks and stuff. Hopeless, bad attitude. Not eveyone is a programmer, and even programmers have better things to do than fix your damned bugs all the time.)
If a bug report is bad (and we all know that many are way out there), be sure to reply courteously and ask for more information, point them to the bug submission FAQ, and be sure to CC the reply to a repository.
If the bug submitter doesn't respond or help with the needed information you have your back covered, because you can say: "I took action. I asked for more information, and that information hasn't been forthcoming".
If anyone have a problem with that response, they should get a lesson in common courtesy.
(Do you think that a carpenter gets phoned up and told: My house has a problem, fix it? No, they get information about where the problem is and other information.)
I need to improve as a programmer when answering bug reports, I need to improve as a bug reporter when contacting some open source projects.
But Robin is right, the idiotic mind set that I'm in wrong or not enlightened because I submit a bug report is pretty annoying.
I hate it each time I have suggestion or a bug to the KMail people where I get the response "it isn't supposed to do that", "are you sure you are doing it right", "have you checked the earlier suggestions", "fix it yourself".
The last one is a laugh.
Not that problematic
Well, perhaps it is. One thing, though, only the initial release of a software package needs updates of most information. The announcements of new versions would only include:
New file location
New version number
Perhaps a bit more, but my point is that I can bear the burden of registering with many sites the first time, but later on when I perform an update, it gets tiresome to surf the web forms.