go.tools: create release-branch.go1.2

[adg]

Once we know which version of the go.tools repo to use in the 1.2 release, we should set
the defaultToolTag constant in misc/dist.

[adg]

Comment 2:

This issue was closed by revision 73d7d12.

Status changed to Fixed.

[rsc]

Comment 3:

There should be a release-branch.go1.2 in go.tools just like in the main repo, and
misc/dist should use it.
There are going to be point release fixes, and they need to be processed like in the
main repo, not just "grab a new tip" from the subrepo.

Status changed to Accepted.

[minux]

Comment 4:

should we do the same for all the other sub-repos?
so that users of older Go releases are at least able to use older version of the packages
in sub-repos.
see also issue #6548.

[adg]

Comment 5:

https://code.google.com/p/go/source/detail?r=da4bed44f661a8c0728a3b21c3c6f42914891653
@minux: they're really separate issues. I think we only need this branch because we're
releasing binaries of the tools from the go.tools repo. That's not true of the other
repos.

Status changed to Fixed.