I think the hostility comes from the fact that you're presenting yourself as being intelligent enough to ask for code samples, or direct "proof", but too lazy to bother to go find them yourself. Even after being told it's all public, and being given links to release notes, you still insist others do the work to provide you with specific answers and details.

For example, I as a user (not a developer) noted hildon-desktop in PR1.3 had a memory leak, as it's use would go up every day for me. It could have been hildon-desktop, some default widget, the way something was called in a library, a QT related leak... I don't know the specifics. I do know that when I installed CSSU, it stopped doing it. Your response was essentially "pics or it didn't happen", asking for "proof" of an exact diff of where that memory leak occurred, and what patch fixed it. Doesn't that seem a bit childish to you?

If I asked for "proof" that the World Trade Center was hit on 9/11, you'd probably tell me "Google it!" And if I said I wanted you to provide links, after you said to google it and presented a link to the CBS video archive page, would you provide more links, or scoff at me and treat me like an idiot for not using the tools you pointed me at earlier?

That's what's happening here. You've been told where the change logs are, and where the source is at. Yet you still continue to ask for exact details and "proof". Said simply: When you act like a child, people tend to treat like one.

That on the other hand is great. Being willing to actively do something to make the wiki more reflective of the work going on in the project would be much appreciated. Given the choice between spending an hour updating a wiki page to show details of things done vs doing more work, most coders would choose the later. As a result, wiki's tend to be maintained more by people that are not coders, who do just what you've now said you did: Look over change logs and check-in comments and update the wiki to match.

Doing that is not only a huge plus for the community, but it also causes developers to use the wiki more frequently, since all they need to do then in make minor corrections, vs entering all the data by hand. That frees them up to do more development, and makes them happy at the same time. ( I say this as both a developer and as someone who's done this for public projects. )