From 7b3e26987dfac934980a09a0d99896344eab402a Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Mon, 9 Dec 2019 06:19:36 -0800 Subject: [PATCH] doc: clarify Tier 2 implications in BUILDING.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Clarify the explanation of Tier 2 platforms and binary releases. PR-URL: https://github.com/nodejs/node/pull/30866 Reviewed-By: Ben Noordhuis Reviewed-By: Michaël Zasso Reviewed-By: Beth Griggs Reviewed-By: Colin Ihrig Reviewed-By: Gireesh Punathil Reviewed-By: Richard Lau Reviewed-By: Luigi Pinca Reviewed-By: Trivikram Kamat Reviewed-By: Michael Dawson Reviewed-By: Rod Vagg --- BUILDING.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/BUILDING.md b/BUILDING.md index dec0dc868f0c82..f6a2130137c783 100644 --- a/BUILDING.md +++ b/BUILDING.md @@ -70,9 +70,8 @@ There are three support tiers: Test failures on tier 1 platforms will block releases. * **Tier 2**: These platforms represent smaller segments of the Node.js user base. The Node.js Build Working Group maintains infrastructure for full test - coverage. Test failures on tier 2 platforms will block releases. Delays in - release of binaries for these platforms are acceptable where necessary due to - infrastructure concerns. + coverage. Test failures on tier 2 platforms will block releases. + Infrastructure issues may delay the release of binaries for these platforms. * **Experimental**: May not compile or test suite may not pass. The core team does not create releases for these platforms. Test failures on experimental platforms do not block releases. Contributions to improve support for these