Skip to content

docs: clarify OS platform validation coverage #23625

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
qiancai wants to merge 2 commits into
base: release-8.5
Choose a base branch
from
+2 −2
Open

docs: clarify OS platform validation coverage #23625

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5f6709b
Update hardware-and-software-requirements.md
qiancai Aug 27, 2026
bf8069f
Update hardware-and-software-requirements.md
qiancai Aug 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions hardware-and-software-requirements.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ This document describes the software and hardware requirements for deploying and

In v8.5 LTS, TiDB ensures multi-level quality standards for various combinations of operating systems and CPU architectures.

+ For the following combinations of operating systems and CPU architectures, TiDB **provides enterprise-level production quality**, and the product features have been comprehensively and systematically verified:
+ **Tested and validated platforms.** In the following operating system and CPU architecture combinations, each TiDB release is fully validated through PingCAP's systematic test matrix. These combinations are recommended for production deployment.

@qiancai qiancai Aug 27, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
+ **Tested and validated platforms.** In the following operating system and CPU architecture combinations, each TiDB release is fully validated through PingCAP's systematic test matrix. These combinations are recommended for production deployment.
+ **Tested and validated platforms.** For the following combinations of operating systems and CPU architectures, each TiDB release is validated against PingCAP's systematic test matrix. These combinations are recommended for production deployment.

@qiancai qiancai Aug 27, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reason:

  • "In the following ... combinations" is less idiomatic than "For the following combinations of ...".
  • "fully validated" is unnecessarily absolute and could imply exhaustive validation beyond the defined test matrix.
  • "Validated against PingCAP's systematic test matrix" more precisely communicates that the distinction is based on release QA coverage rather than an absolute product-quality guarantee.


<table>
<thead>
Expand Down Expand Up @@ -75,7 +75,7 @@ In v8.5 LTS, TiDB ensures multi-level quality standards for various combinations
>
> Support for Red Hat Enterprise Linux 9.x starts from [TiUP](https://github.com/pingcap/tiup/releases) v1.16.5.

+ For the following combinations of operating systems and CPU architectures, you can compile, build, and deploy TiDB. In addition, you can also use the basic features of OLTP, OLAP, and the data tools. However, because these combinations have not undergone comprehensive and systematic testing, TiDB **does not guarantee enterprise-level production quality**:
+ **Compatible platforms.** In the following combinations, TiDB can compile, build, and deploy, and supports OLTP, OLAP, and the data tools. These combinations are not included in the systematic per-release test matrix; compatibility is verified through build and deployment verification and extensive production usage by TiDB users. For production deployments on these platforms, contact PingCAP to confirm support coverage under your subscription.

@qiancai qiancai Aug 27, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
+ **Compatible platforms.** In the following combinations, TiDB can compile, build, and deploy, and supports OLTP, OLAP, and the data tools. These combinations are not included in the systematic per-release test matrix; compatibility is verified through build and deployment verification and extensive production usage by TiDB users. For production deployments on these platforms, contact PingCAP to confirm support coverage under your subscription.
+ **Compatible platforms.** In the following combinations, TiDB can be compiled, built, and deployed, and supports OLTP, OLAP, and data tools. These combinations are not included in the systematic per-release test matrix; compatibility is verified through build and deployment verification and extensive production usage by TiDB users. For production deployments on these platforms, contact PingCAP to confirm support coverage under your subscription.

@qiancai qiancai Aug 27, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TBD, “build and deployment verification and extensive production usage by TiDB users.” is confusing, as it implies that all of these compatible combinations have been extensively verified and used in production envrionments too.


<table>
<thead>
Expand Down