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

remove incorrect statement (for golang.org/issue/40206)

Dmitri Shuralyov 2020-08-21 17:52:51 -04:00
parent 22b4f2312c
commit 32013d6f7e
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
MinorReleases.md

@ -1,6 +1,6 @@
Our default decision should always be to not backport, but fixes for **security issues**, **serious problems with no workaround**, and **documentation fixes** are backported to the most recent two release branches, if applicable to that branch. (for example, the most current two release branches are `release-branch.go1.13` and `release-branch.go1.14`, from which new `Go 1.13.x` and `Go 1.14.x` releases are cut) Fixes for experimental ports are generally not backported.
A “serious” problem is one that prevents a program from working at all. "Use a more recent stable version" is a valid workaround, so very few fixes will be backported to both previous issues.
A “serious” problem is one that prevents a program from working at all.
As soon as an interested party thinks an issue should be considered for backport, they open one or two “child” issues titled like `package: title [1.9 backport]`. The issue should include a link to the original issue and a short rationale about why the backport might be needed.