-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
proposal: all: drop netbsd/arm64 port #50451
Comments
Sorry that we collectively dropped the ball on this issue. As for myself, with everything going on around us, it has been hard to dedicate the needed attention to this. I asked around in the NetBSD development community for some insights. |
This proposal has been added to the active column of the proposals project |
@bsiegert, any progress on this? This issue is not so much about deciding whether to drop netbsd/arm64 or whether it's good but just about whether it is meeting the maintenance bar. Right now it's not. Thanks. |
The current theory is that it is a fixed bug, and/or some issue with the current builder. I was going to bring up a second builder machine before making bigger upgrades to the first, particularly as I won't be able to access the machine physically in the next ~week. |
I made some changes to the builder and added a second one, as detailed in #42422. |
The issue that was causing regular failures on this builder (#42422) appears to be fixed. |
Looks like it's fixed for all except for In that case, I withdraw the proposal. |
Thanks everyone!🎉🎉 |
This proposal has been declined as retracted. |
The requirements for a Go port include that “At least one developer must be named (and agree) to maintain the port, by making required updates in a timely manner as architecture or operating system requirements change.”
The only builder currently running for
netbsd/arm64
is failing frequently with a platform-specific failure mode that cannot be easily skipped (#42422), and the last activity on the tracking issue from the folks I believe to be the port maintainers (@bsiegert, @coypoop, and possibly @4a6f656c?) was over a year ago — a substantial amount of time to look into the issue even given the upheaval of the past couple of years.Given the lack of progress on getting the builder to a passing state, I think it is time to drop this port from the mainline Go project.
The text was updated successfully, but these errors were encountered: