Commit 3ac40b9
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 <info@bnoordhuis.nl>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Reviewed-By: Rod Vagg <rod@vagg.org>1 parent ac5de4f commit 3ac40b9
1 file changed
Lines changed: 2 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -70,9 +70,8 @@ There are three support tiers: | |||
| 70 | 70 | Test failures on tier 1 platforms will block releases. | |
| 71 | 71 | * **Tier 2**: These platforms represent smaller segments of the Node.js user | |
| 72 | 72 | 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. | ||
| 76 | 75 | * **Experimental**: May not compile or test suite may not pass. The core team | |
| 77 | 76 | does not create releases for these platforms. Test failures on experimental | |
| 78 | 77 | platforms do not block releases. Contributions to improve support for these | |
0 commit comments