Updated MinorReleases (markdown)

Andrew Bonventre 2018-09-13 14:43:03 -04:00
parent 90e7816b4d
commit 65bdb59e41

@ -1,4 +1,4 @@
Fixes for regressions, security issues, and serious problems with no workaround are backported to the two supported major releases. For example a fix developed during the 1.11 cycle will be backported to a 1.9.x (if applicable) and 1.10.x release.
Our default decision should always be to not backport, but fixes for **regressions**, **security issues**, and **serious problems with no workaround** are backported to the two supported major releases. For example a fix developed during the 1.11 cycle will be backported to a 1.9.x (if applicable) and 1.10.x release.
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.