From 2c5d1003e924c867cfe20df1e17564bfc50d478f Mon Sep 17 00:00:00 2001 From: Dmitri Shuralyov Date: Thu, 1 Nov 2018 13:20:35 -0400 Subject: [PATCH] Write down backporting policy for experimental ports (e.g., WebAssembly). --- MinorReleases.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MinorReleases.md b/MinorReleases.md index ba951a26..9976cf04 100644 --- a/MinorReleases.md +++ b/MinorReleases.md @@ -1,4 +1,4 @@ -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 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 **security issues**, **serious problems with no workaround**, and **documentation fixes** 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. Fixes for experimental ports are not backported. A “serious” problem is one that prevents a program from working at all.