Am 25.01.2011 15:35, schrieb Anthony Liguori: > On 01/25/2011 03:57 AM, Kevin Wolf wrote: >> Am 25.01.2011 00:06, schrieb Paolo Bonzini: >> >>> ... or at least "git mv Changelog Changelog.old"? >>> >>> It only goes back to 0.12.0 so that there is hardly a place in the git >>> repo to look for new features in 0.13 and 0.14. >>> >> Or maybe update it? >> >> I find it rather unfriendly to our users to say "Here is a new release. >> In the unlikely case that you really want to know what has changed, >> please bother yourself to filter the interesting stuff out of these >> thousand git commits". >> > > Logistically, I prefer doing highlights in a mail verses having a > committed file. A Changelog file needs to be committed prior to tagging > a release and cannot be enhanced after the fact. The nice bit about an > email is that folks can respond to it with additional details. > > A wiki page (similar to what kernel newbies does) would be nice to > supplement what's included in the release notes.
We do have a wiki page "ChangeLog" and there are more than enough links to it, it just hasn't been updated since 0.12.5. I don't really care too much in which way we do it. But for 0.13 we don't have any kind of a high-level changelog on qemu.org or in the release tarball, and I think we should. Kevin
