Tangential, but I'd suggest changing the milestone name to go1.4-bootstrap and the milestone description, it's quite misleading

We will likely never make a Go 1.4.4 release. The only reason to do so would be to ease bootstrapping of newer Go releases

a) we regularly publish new go1.4-bootstrap releases to "ease bootstrapping" b) they're not called go1.4.4, they're called go1.4-bootstrap

I'd suggest changing the milestone name to go1.4-bootstrap and the milestone description

Huh. Apparently I can edit milestones (!). Done. Anyone who cares about the text there should review. cc @kevinburke in case maintner cares. I left the capital "G" in the milestone name to match the others for now.

Huh. Apparently I can edit milestones

@josharian me too. I think it's normal (for users marked as Member).

I asked (instead of changing it myself) because I wasn't sure people would be fine with it. New description looks fine to me BTW.

I asked (instead of changing it myself) because I wasn't sure people would be fine with it.

Guess I'll ask forgiveness instead of permission then. :) I wish GitHub had all this config in the repo itself, so this could be codereviewed.

@josharian can you explain what's left to do here? AFAIK the no-pie issue is fixed and the patch already is on the 1.4 branch, which we document (in the install from source page):

To build a bootstrap toolchain from source, use either the git branch release-branch.go1.4 or go1.4-bootstrap-20171003.tar.gz, which contains the Go 1.4 source code plus accumulated fixes to keep the tools running on newer operating systems.

Can this issue be closed?

@ALTree yes, thanks.