cybercyst/go
1
0
Fork 0
mirror of https://github.com/golang/go.git synced 2025-05-05 15:43:04 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Be clearer about Go team needing to accept new ports and why.

Russ Cox 2020-05-06 14:34:10 -04:00
parent c29178c1b8
commit d852cd8908
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
PortingPolicy.md

@ -8,6 +8,8 @@ The goal of this policy is to avoid the accumulation of incomplete or broken por
Before any code relating to a port can be added to the main Go repository, the following must all be done:
* A proposal must be filed and accepted in which the Go team accepts overall responsibility for having the new port in the core Go tree. In general, each new port carries an upkeep cost separate from the direct maintenance. That cost varies by port, depending on how similar a new port is to existing ones. The cost must be balanced by an overall benefit in the form of potential new users or use cases for Go.
* 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.
* A developer must be named (and agree) to maintain the builder, the machine trying each git revision and providing data for https://build.golang.org.
@ -20,8 +22,6 @@ Once those conditions are satisfied, the Go team can accept the port and begin t
Any port started during a release cycle must be finished (all.bash passing, builder reporting "ok") before the corresponding release freeze, or else the code will be removed at the freeze.
Because having any port entails a certain maintenance burden on the entire Go development team, not just the port's maintainer, the Go team may refuse a port meeting the above criteria if the port is judged not to reach enough users. This exception is intended to be used rarely, mainly to avoid maintaining ports for toy or hobby operating systems or experimental hardware that is not widely available.
# Other repositories
Although it is not part of the core repository, the x/sys repository should add support for the new port before the release happens because it is the official place to add new system calls.