x/build: surface port maintainers on dev.golang.org #50933
Labels
Builders
x/build issues (builders, bots, dashboards)
FeatureRequest
Issues asking for a new feature that does not need a proposal.
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
https://dev.golang.org/owners currently lists code owners for a large subset of packages in the Go project.
However, when it comes to tracking down build and test failures, code owners are only half of the story. Our requirements for a new port also require that “[a]t 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.”
When we spot a port-specific issue, we need to know who to loop in to make the updates needed to resolve that issue.
Some of that information is currently embedded in the
Owners
field for the builder information inx/build/dashboard/builders.go
, but:Either
dev.golang.org/owners
or a similar page ondev.golang.org
should identify port owners explicitly byGOOS
andGOARCH
.(CC @golang/release for prioritization)
The text was updated successfully, but these errors were encountered: