I have to admit it: I broke the 1.02 version of Encode::IMAPUTF7, but I didn't mean to hide it.
The version have two changes. A code cleanup, which among other minor things make the indentation and coding style consistent, and an RFC compliance fix with a patch from the bug submitter. The patch used the old coding style, so I had to aply it by hand — and in this process I broke some functionality.
Even though I didn't use his patch, I did thank the original submitter in the changelog. It appears that I shouldn't have done that. For the last two days he has tried to contact me to get his name removed from the changelog. He even looked up my phone number and probably tried to call me twice and texted me once. Well, version 1.04 just being uploaded have a revised Changes file.
So what can I do to avoid this another time?
The first thing is that I have moved the code to github. This enables contributers to patch the latest version.
The second change is to improve testing. It was quite easy to write test cases for the bug. If I had done that the broken version would never have been uploaded.
I still believe that the phrasing 'thanks to John Doe' was right and doesn't imply blame allocation. But in the future I should at least link to the changeset at github.
Any other recommendation for best practices for writing Changes files without making contributers mad?