pan3793 commented on PR #6864: URL: https://github.com/apache/hadoop/pull/6864#issuecomment-2154900881
Use Spark `branch-3.4` as an example, the `branch-3.4` should always be under the release-ready state, when a patch release is called, RM(release manager) just performs two commits: - Bump version from 3.4.0-SNAPSHOT to 3.4.1, create a tag on this commit v3.4.1-rc0, and "pom changes, references, diffs" should be happened here, by scripts. - Bump version from 3.4.1 to 3.4.1-SNAPSHOT, similar with above. <img width="637" alt="image" src="https://github.com/apache/hadoop/assets/26535726/a3d60fd4-2d38-4316-affa-a6f96d21aed8";> If something goes wrong, the RC fails, then repeat the work until the release is out. This branch model is adopted by many other Apache projects like Apache Kyuubi, and Apache Celeborn. For Kyuubi, we have a release guide https://kyuubi.readthedocs.io/en/master/contributing/code/release.html -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
