- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for Next (0.12 sec)
-
doc/README.md
At the start of a release development cycle, the contents of `next` should be deleted and replaced with those of `initial`. From the repo root: > cd doc > rm -r next/* > cp -r initial/* next Then edit `next/1-intro.md` to refer to the next version. To prepare the release notes for a release, run `golang.org/x/build/cmd/relnote generate`.
Plain Text - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Fri Apr 26 21:24:36 GMT 2024 - 1.9K bytes - Viewed (0) -
api/README
the new API. This helps with our end-of-cycle audit of new APIs. The same requirement applies to next/* (described below), which will become a go1.XX.txt for XX >= 19. The next/ directory contains the only files intended to be mutated. Each file in that directory contains a list of features that may be added to the next release of Go. The files in this directory only affect the warning output from the go api tool. Each file should be named
Plain Text - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Wed Jan 31 19:22:50 GMT 2024 - 1.2K bytes - Viewed (0) -
.github/PULL_REQUEST_TEMPLATE
This PR will be imported into Gerrit with the title and first comment (this text) used to generate the subject and body of the Gerrit change. **Please ensure you adhere to every item in this list.** More info can be found at https://github.com/golang/go/wiki/CommitMessage + The PR title is formatted as follows: `net/http: frob the quux before blarfing` + The package name goes before the colon
Plain Text - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Wed Feb 21 02:07:46 GMT 2018 - 1.2K bytes - Viewed (0) -
.gitattributes
# # We'll prevent accidental CRLF line endings from entering the repo # via the git-codereview gofmt checks and tests. # # See golang.org/issue/9281.
Plain Text - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Mon Jun 08 15:31:43 GMT 2020 - 639 bytes - Viewed (0)