Skip to content

Commit b9160b4

Browse files
committed
Remove official/unofficial from previous releases
1 parent 4d715ae commit b9160b4

1 file changed

Lines changed: 12 additions & 20 deletions

File tree

‎apps/site/pages/en/about/previous-releases.mdx‎

Lines changed: 12 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -23,30 +23,22 @@ Full details regarding the Node.js release schedule are available [on GitHub](ht
2323

2424
<PreviousReleasesTable />
2525

26-
## Official vs. Community Installation Methods
26+
## Recommended and community installation methods
2727

28-
The Node.js website provides several non-interactive installation methods, including command-line interfaces (CLIs), operating system (OS) package managers (e.g., `brew`), and Node.js version managers (e.g., `nvm`).
28+
The Node.js website provides several non-interactive installation methods on the Downloads page, including command-line interfaces (CLIs), operating system (OS) package managers (e.g., `brew`), and Node.js version managers (e.g., `nvm`).
2929

30-
To highlight and promote community contributions, the Node.js project introduced a revised Downloads page categorizing installation methods as either “Official” or “Community.” This provides users with increased flexibility and choice. To ensure clarity, we’ve defined criteria for each category.
30+
To highlight and promote community contributions, the Node.js project introduced a revised Downloads page categorizing installation methods as either “Recommended” or “Community.” This provides users with increased flexibility and choice, while keeping a short, curated list for those who want a straightforward starting point.
3131

32-
### Official Installation Methods
32+
Anyone can propose a new installation method for the Downloads page. While the Node.js project makes the final call on what gets listed, proposals are evaluated against the criteria below.
3333

34-
Installation methods designated as “Official” must meet the following requirements:
34+
“Recommended” methods are selected for their reliability and close alignment with official releases, and meet the following criteria (in addition to all “Community” criteria):
3535

36-
| Requirements (Official Installation Methods) |
37-
| :------------------------------------------------------------------------------------------------------------------------------- |
38-
| New Node.js releases must be available simultaneously with the official release. |
39-
| Project maintainers must have a close relationship with the Node.js project, including direct communication channels. |
40-
| Installation method must download official binaries bundled by the Node.js project. |
41-
| Installation method must not build from source when pre-built binaries are available, nor should it alter the official binaries. |
36+
- “Recommended” methods make new Node.js releases available simultaneously with the official release.
37+
- “Recommended” methods use the official Node.js binaries without alteration, only building from source when pre-built binaries are not available.
38+
- “Recommended” methods have a close relationship with the Node.js project, including direct communication channels.
4239

43-
### Community Installation Methods
40+
“Community” methods are additional installation methods also available on the Downloads page, and meet the following criteria:
4441

45-
Community installation methods included on the self-service download page (located at /download) must also adhere to a minimum set of criteria:
46-
47-
- **Version Support:** Must support all currently supported, non-End-of-Life (EOL) Node.js versions.
48-
- **OS Compatibility:** Must function on at least one officially supported Operating System (OS).
49-
- **Broad OS Support:** Cannot be limited to a subset of OS distributions or versions.
50-
- For example, an installation method claiming compatibility with “Windows” must function on “Windows 10”, “Windows 11”, and all their editions (including server versions).
51-
- Similarly, an installation method claiming compatibility with “Linux” must be installable on all major Linux distributions, not just a specific subset. It cannot rely on distribution-specific package managers like `apt` or `dnf`.
52-
- **Free and Open Source:** Must be free to use and open source, must not be sold as a commercial product, and must not be a paid service.
42+
- “Community” methods must support all currently supported, non-End-of-Life (EOL) Node.js versions.
43+
- “Community” methods must function on at least one officially supported Operating System (OS), and must not be limited to a subset of OS distributions or versions.
44+
- “Community” methods must be free to use and open source, must not be sold as a commercial product, and must not be a paid service.

0 commit comments

Comments
 (0)