-
Notifications
You must be signed in to change notification settings - Fork 18.1k
x/build/internal/releasetargets: distribute official binaries for netbsd/arm64 #41706
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
/cc @golang/osp-team |
To make a release, a builder is required (it's used in a releaselet mode). The |
Yes. @cagedmantis was going to work on a non-reverse builder, until that's landed, mine should be good. |
@bsiegert the non-reverse builder is still planned. |
Excellent, thanks.
Carlos Amedee <[email protected]> schrieb am Mo. 5. Okt. 2020 um
21:58:
@bsiegert <https://github.com/bsiegert> the non-reverse builder is still
planned.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#41706 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGTQGWSSX6MT4P7PPFZ7E3SJIQN3ANCNFSM4R6V5X3A>
.
--
Benny
|
We haven't yet gotten to this for Go1.16, but it shouldn't block the release. Punting to Go1.17; thank you everyone for the discussion and for the patience. |
Has any progress been made on this? Otherwise I'll punt it to backlog, since it's already been punted for one release. |
@mknyszek Thanks for checking in. This issue is currently in NeedsDecision state, and I added it to a list of issues for the release team to review for 1.17 during a meeting tomorrow, so I expect we'll update it soon. |
If it helps: having official binaries for netbsd/arm64 would be good for the NetBSD packages. We have https://pkgsrc.se/lang/go-bin with official binaries for bootstrapping, but we had to use a NetBSD Foundation build for arm64. |
We discussed this on the release team and decided that we cannot add this binary release target in time for Go 1.17 unfortunately. Each additional release target carries some overhead and risk for the release process, and given our current state, we don't have the room to take this on before completing some work to reduce that overhead and risk. We would like to be able to do this at some point, but we won't be able to get to it to 1.17 because there isn't time given the amount of work still needed to done to release 1.17. I'll move this to Backlog for now so we can come back to this when there is more time. @bsiegert Thanks for additional context in the comment above, it is helpful for us to make a more informed decision about which ports we want to prioritize adding binary releases for. We've discussed that we also want to make it a prerequisite to have a more detailed cost/benefit analysis as part of prioritizing potential ports to add binaries for. When we're ready to make progress here, we may try to find out even more information. |
This is done as part of #53862. Binary releases for the |
Now that the netbsd/arm64 port has stabilized somewhat, I would like to ask for it to be part of the release binaries. That is, the 1.16 release should contain a .tar.gz with binaries for netbsd/arm64.
This would be useful for bootstrapping: In the OS packages (pkgsrc), we need a Go version to build Go itself. So far, we have been using a patched 1.14.2 that was built on a NetBSD Foundation machine. An official binary would be much simpler.
The text was updated successfully, but these errors were encountered: