It seems contradictory in this case, but not when you consider all the previous releases. With previous releases there has been what I call a "point-release-tr

It seems contradictory in this case, but not when you consider all the previous releases. With previous releases there has been what I call a "point-release-triggering fix". That is, a fix that simply cannot wait until the next release (for example, one that fixes a security hole). In those cases there is some advisory warning in the announcement. In this case, it had been 3 months since the last release and a few point-release-worthy (but not point-release-triggering) fixes had accumulated, so we though it's probably worth getting them out there before 1.3 (in another 3 months' time). I have considered your points. That's why (in response to point 1) I have linked to the changes directly from the release announcement and acknowledged in my message that perhaps I should write the changes up in future, and (in response to point 2) I issued the point release in the first place and submitted the announcement post here so that Go users would know to upgrade.