That sounds useful -- sort of an email saying things like, "We had something go wrong with the frobitzer and a whole bunch of people wrote us about that, and there's this thing someone mentioned that apparently has been broken since the dawn of time and we can't figure out how nobody had trouble before, and..."?

I might find that interesting; I might not. I can see how that might fit into the overall process now, though, and I think that helps (in a way that's sort of like the "form follows function" edict). It's a thing I probably wouldn't find as intrinsically interesting as the code reports, but I expect it could be written in a way that I would enjoy reading it regardless. Who knows?