I started by mentioning upstream golang-announce in the README.md, in case someone sees our repo without being aware of the upstream mailing list. (Suggested by an internal user when I asked for thoughts on removing the links from our announcements.)
I realized that the internal links could probably be organized better (a non-Microsoft user doesn't care about either of them, but someone in Microsoft probably cares about both). Also, some of the info was duplicated.
Also changed Completed builds of Go to Signed builds of Go. I don't think a "Completed build" is a common term... "pre-built" would be the right term for that. But I think changing it to something unique about those builds (signed) is more useful.
I started by mentioning upstream golang-announce in the README.md, in case someone sees our repo without being aware of the upstream mailing list. (Suggested by an internal user when I asked for thoughts on removing the links from our announcements.)
I realized that the internal links could probably be organized better (a non-Microsoft user doesn't care about either of them, but someone in Microsoft probably cares about both). Also, some of the info was duplicated.
Also changed
Completed builds of Go
toSigned builds of Go
. I don't think a "Completed build" is a common term... "pre-built" would be the right term for that. But I think changing it to something unique about those builds (signed) is more useful.