Do any teams in Google write a human readable change log?
The only one I know of that comes close is the Chrome team, which gets by with a blogspot[1] that sometimes has nice lists of the changes (sometimes in list form, sometimes in a paragraph with loads o' commas), and sometimes says stuff like:
It's not a huge deal in this case, but if you release a version and link to it and want us to know why its significant, it would be nice to find out why in English instead of SVN-ese.
Compare this to the great, readable version that Firefox offers[3]
The only one I know of that comes close is the Chrome team, which gets by with a blogspot[1] that sometimes has nice lists of the changes (sometimes in list form, sometimes in a paragraph with loads o' commas), and sometimes says stuff like:
> A partial list of changes in this build is available in the SVN revision log http://build.chromium.org/f/chromium/perf/dashboard/ui/chang...
And here with Go 1.2.1 we get this[2].
It's not a huge deal in this case, but if you release a version and link to it and want us to know why its significant, it would be nice to find out why in English instead of SVN-ese.
Compare this to the great, readable version that Firefox offers[3]
~~~
[1] http://googlechromereleases.blogspot.com/
[2] https://code.google.com/p/go/source/list?name=release-branch...
[3] https://www.mozilla.org/en-US/firefox/27.0.1/releasenotes/