cmd/go: executables are sometimes named after their module's last element, not directory [1.12 backport]

[gopherbot]

@mvdan requested issue #27283 to be considered for backport to the next 1.12 minor release.

@gopherbot please backport to 1.12

[julieqiu]

@mvdan - there isn't a reason provided in the gopherbot message. Would you mind providing one for this backport?

[mvdan]

See Filippo's comment in the original thread.

Is there a convention to add the reason for the backport in the backport issue directly?

[gopherbot]

Change https://golang.org/cl/167384 mentions this issue: [release-branch.go1.12] cmd/go: fix the default build output name for versioned binaries

[gopherbot]

Closed by merging 746edd4 to release-branch.go1.12.

[dmitshur]

Is there a convention to add the reason for the backport in the backport issue directly?

@mvdan Yes. I'll quote from https://golang.org/wiki/MinorReleases (emphasis mine):

As soon as an interested party thinks an issue should be considered for backport, they open one or two “child” issues titled like package: title [1.9 backport]. The issue should include a link to the original issue and a short rationale about why the backport might be needed.

When asking gopherbot to backport an issue, the reason should be included in that message. That
way it ends up in the backport issue description (e.g., see #30266 (comment)), and that helps with making the decision of whether a cherry-pick candidate issue should be accepted. Thanks!

[gopherbot]

Change https://golang.org/cl/167617 mentions this issue: Revert "[release-branch.go1.12] cmd/go: fix the default build output name for versioned binaries"

[gopherbot]

Closed by merging 32355f5 to release-branch.go1.12.