achterin

sorry but thats bullsh**. even linus torvalds is able to give a proper changelog for the kernel rc's. git and some sed magic and you're done. the changelog doesn't have to be proper formated or sorted by type. also the pure git log output will be enough. for stable your argument is valid in my opinion but for any experimental update a short, non formated log will do it. anyway, i don't understand why people are so obsessed with changelogs. i think proper and fast updates are more useful than an exact changelog.

you are right, but even for stable maintenaince it would be useful to know what changes they've made. before the netcode changes they released a exp update and pushed the tested exp changes to stable, so you knew what you will get on stable. but now they update exp and stable independantly from each other and don't give any appropriate information to the users. sometimes they only make changes to monitor the hive, sometimes they push new content. and on every update now its the same, servers go down and up again, hicks posts some short information on twitter (without saying what they did) and a few minutes later people start asking what they've changed. if they will tell the ppl "no new stuff today, only hive monitoring changes" everyone knows what to expect.

it would be nice, if they tell the people what they do on maintainance, otherwise people will keep asking when the new update gets released.