4 ms·

> We strictly include only critical fixes for issues for which there is no workaround. For Go point releases, most people should just install them and move on.

by hrjet 13y ago

> We strictly include only critical fixes for issues for which there is no workaround. For Go point releases, most people should just install them and move on. For 99.9% of Go programmers there is "nothing to see here". Isn't that a little contradictory? You are saying all the changes in this release are critical, yet there is "nothing to see here". As I understand it, these changes are critical corner cases but you believe that they are not experienced by 99.9% of the users. However, you should consider two things: 1. Such critical issues might be useful information for users who are not facing those issue currently (but might hit them in the future). 2. Your estimation of 99.9% might be wrong, because not all users might have complained loudly or even realized that there is an issue.

enneff 13y ago
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.
jussij 13y ago
> Isn't that a little contradictory? You are saying all the changes in this release are critical, yet there is "nothing to see here". To quote T. B. Lance 'if it ain't broke don't fix it'

by hrjet 13y ago

enneff 13y ago

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.

jussij 13y ago

> Isn't that a little contradictory? You are saying all the changes in this release are critical, yet there is "nothing to see here". To quote T. B. Lance 'if it ain't broke don't fix it'