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

delete section mentioning obsolete old-style security releases

Dmitri Shuralyov 2022-07-13 17:25:23 -04:00
parent c9130315be
commit 61cbd12e95
1 changed files with 0 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
MinorReleases.md

@ -67,12 +67,3 @@ The Go standard library includes some generated files whose source of truth is o
The commit message should include "Fixes #nnn" to close the backport issue.
(As of Go 1.16, the golang.org/x branch name is always `internal-branch.go1.x-vendor`. In Go 1.15, the name of the golang.org/x branch is `release-branch.go1.x` or `release-branch.go1.x-bundle` in [special cases](https://go.dev/cl/305489).)
## Security releases
Note: This section describes process used for security releases before the [new security policy](https://go.dev/issue/44918) was applied. It is not current.
Security releases preempt the next minor release and need to ship only the security fix.
To avoid rolling back the release branch in that exceptional case, a new release branch is created based on the previous release. For example `release-branch.go1.9-security` is branched from tag `go1.9.4`. The release is tagged from that branch, and the branch is then merged into the main release branch. For example `go1.9.5` is tagged from `release-branch.go1.9-security`, which is then merged into `release-branch.go1.9`.