Skip to content

Commit 3ac40b9

Browse files
Trotttargos
authored andcommitted
doc: clarify Tier 2 implications in BUILDING.md
Clarify the explanation of Tier 2 platforms and binary releases. PR-URL: #30866 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Beth Griggs <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Rod Vagg <[email protected]>
1 parent ac5de4f commit 3ac40b9

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

BUILDING.md

+2-3
Original file line numberDiff line numberDiff line change
@@ -70,9 +70,8 @@ There are three support tiers:
7070
Test failures on tier 1 platforms will block releases.
7171
* **Tier 2**: These platforms represent smaller segments of the Node.js user
7272
base. The Node.js Build Working Group maintains infrastructure for full test
73-
coverage. Test failures on tier 2 platforms will block releases. Delays in
74-
release of binaries for these platforms are acceptable where necessary due to
75-
infrastructure concerns.
73+
coverage. Test failures on tier 2 platforms will block releases.
74+
Infrastructure issues may delay the release of binaries for these platforms.
7675
* **Experimental**: May not compile or test suite may not pass. The core team
7776
does not create releases for these platforms. Test failures on experimental
7877
platforms do not block releases. Contributions to improve support for these

0 commit comments

Comments
 (0)