zjw1111 commented on code in PR #508: URL: https://github.com/apache/paimon-cpp/pull/508#discussion_r4467766758
########## scripts/releasing/README.md: ########## @@ -53,23 +53,53 @@ brew install gzip export PAIMON_GZIP="$(brew --prefix gzip)/bin/gzip" ``` -For example, update all version locations and review the diff: +During release preparation, check the release version metadata: ```bash -scripts/releasing/bump_version.py 0.2.0 0.3.0 -scripts/releasing/bump_version.py --check 0.3.0 +scripts/releasing/bump_version.py --check 0.4.0 ``` -The target version becomes the stable documentation label (for example, -`0.3.0 (stable)`). If its major.minor series differs from the previous stable -series, the previous release is moved to an archived entry. Archived labels -also show the full version, while their identifiers and URLs retain the -major.minor series. Patch releases update the stable label without adding -an archive. The documentation version may track the latest stable release -while the CMake version advances; release preparation updates both to the -target version. Use this command for release -preparation; it also promotes documentation and is not a development-only -version bump. +After publishing `0.4.0`, start the next development cycle and review the diff: Review Comment: I think the README is just an example, no need to modify the version number every time. Also, I feel that the phrase "After publishing `0.4.0`" is too absolute—it makes it look like documentation written exclusively for this specific release. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
