On 14 November 2015 at 04:28, Austin Clements <
aus...@google.com> wrote:
> You beat me to the punch. I was going to suggest that we start thinking
> about a 1.5.2.
\o/
I'm mostly interested in the non-atomic-pointer writes ones and a
couple of ppc64 codegen bugs.
Also, there is the issue that building Go with a very new C toolchain
fails (
https://github.com/golang/go/issues/13114) -- is it appropriate
to fix this in a point release? I'll need to include this patch in any
update of Go in Ubuntu in any case...
> There's at least one project that's rolled back to 1.4 because of some of
> these issues. And we've cherry-picked the fixes for some of these internally
> at Google (12233 and 12894 at least), so they're clearly important to
> Google.
>
> There are still open 1.5.2 bugs, some of which I'd like to fix (I'm working
> on 13143 right now and may have a fix), but they all seem incredibly rare or
> lower priority.
Is there anything I can do to help?
Cheers,
mwh