Skip to content

Commit d42d5eb

Browse files
authored
Merge pull request #351 from chdb-io/version-guide
Add version guide
2 parents 082f6a7 + e24f396 commit d42d5eb

File tree

3 files changed

+92
-0
lines changed

3 files changed

+92
-0
lines changed

README-zh.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -231,6 +231,10 @@ sess.close()
231231

232232
- Demo chDB at [ClickHouse v23.7 livehouse!](https://t.co/todc13Kn19) and [Slides](https://docs.google.com/presentation/d/1ikqjOlimRa7QAg588TAB_Fna-Tad2WMg7_4AgnbQbFA/edit?usp=sharing)
233233

234+
## 版本说明
235+
236+
请查看 [VERSION-GUIDE.md](VERSION-GUIDE.md) 获取更多信息。
237+
234238
## 相关论文
235239

236240
- [ClickHouse - Lightning Fast Analytics for Everyone](https://www.vldb.org/pvldb/vol17/p3731-schulze.pdf)

README.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -474,6 +474,10 @@ There are something you can help:
474474

475475
We welcome bindings for other languages, please refer to [bindings](bindings.md) for more details.
476476

477+
## Version Guide
478+
479+
Please refer to [VERSION-GUIDE.md](VERSION-GUIDE.md) for more details.
480+
477481
## Paper
478482

479483
- [ClickHouse - Lightning Fast Analytics for Everyone](https://www.vldb.org/pvldb/vol17/p3731-schulze.pdf)

VERSION-GUIDE.md

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
# chDB Version Numbering Rules
2+
3+
## Version Format
4+
5+
chDB follows the [Semantic Versioning (SemVer)](https://semver.org/) specification, with version format: `vX.Y.ZbN`
6+
7+
### Version Components
8+
9+
- **First digit (1)** - **Major Version**
10+
- Contains incompatible API changes or major architectural adjustments
11+
- Requires compatibility checks when upgrading
12+
- Real examples: `v1.0``v2.0``v3.0`
13+
14+
- **Second digit (2)** - **Minor Version**
15+
- New features and backward-compatible API extensions
16+
- Generally no breaking changes, safe to upgrade
17+
- Real examples: `v3.0.0``v3.1.0``v3.2.0``v3.3.0``v3.4.0`
18+
19+
- **Third digit (3)** - **Patch Version**
20+
- Backward-compatible bug fixes and minor optimizations
21+
- Users can upgrade with confidence, no compatibility concerns
22+
- Real examples: `v3.1.0``v3.1.1``v3.1.2`
23+
24+
- **Suffix b0** - **Beta Version Identifier**
25+
- Indicates beta test version, numbering starts from 0
26+
- Used for feature testing before official release
27+
- Real examples: `v2.2.0b0``v2.2.0b1``v2.2.0`
28+
29+
## Beta Version Overview
30+
31+
### What is a Beta Version
32+
33+
Beta versions are pre-release versions before the official release, used for:
34+
- Testing new feature stability
35+
- Collecting user feedback
36+
- Discovering potential issues
37+
38+
### Beta Version Characteristics
39+
40+
- **pip default installation ignores** beta versions
41+
- Features are relatively stable but may have unknown issues
42+
- Suitable for testing environments, use caution in production
43+
44+
### Installing Beta Versions
45+
46+
```bash
47+
# Install latest beta version
48+
pip install --pre chdb
49+
50+
# Install specific beta version
51+
pip install chdb==2.2.0b0
52+
```
53+
54+
## Real Version Release Examples
55+
56+
### Latest Version Series (v3.x)
57+
- **v3.4.0** (July 2025) - Latest stable version, upgraded ClickHouse to v25.5.2.47
58+
- **v3.3.0** - Added JSON type support and storage metrics
59+
- **v3.2.0** - Added streaming query API
60+
- **v3.1.2** - Fix version, resolved multiple bugs
61+
- **v3.1.1** - Fix version, performance optimizations
62+
- **v3.1.0** - Added JSON type support
63+
- **v3.0.1** - Fix version, resolved v3.0.0 issues
64+
- **v3.0.0** - Major version, introduced connection-based API which is also the default implementation. Users upgrade from v2.x to v3.x should be careful.
65+
66+
### Beta Version Series Examples
67+
- **v2.2.0b0** - First beta version of v2.2.0
68+
- **v2.2.0b1** - Second beta version of v2.2.0, fixed issues found in b0
69+
- **v2.2.0** - Official version release
70+
71+
## Version Upgrade Recommendations
72+
73+
### Safe Upgrades
74+
- **Patch versions** (e.g., v3.1.0 → v3.1.2): Can upgrade directly
75+
- **Minor versions** (e.g., v3.1.x → v3.2.x): Usually safe to upgrade, testing recommended
76+
77+
### Cautious Upgrades
78+
- **Major versions** (e.g., v2.x → v3.x): Need compatibility checks, may require code changes
79+
- **Beta versions**: Only recommended for testing environments
80+
81+
### Production Environment Recommendations
82+
- Use stable versions (no beta suffix)
83+
- Upgrade to latest bugfix version first(eg. v3.1.0 -> v3.1.2)
84+
- Verify compatibility in testing environment before upgrading

0 commit comments

Comments
 (0)