This is an automated email from the ASF dual-hosted git repository.
danny0405 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hudi.git
The following commit(s) were added to refs/heads/master by this push:
new 8eed6aefbc4 [MINOR] Update release guide (#11433)
8eed6aefbc4 is described below
commit 8eed6aefbc4de9ea5426fefa296c0723bbc3fb14
Author: Sagar Sumit <[email protected]>
AuthorDate: Tue Jun 11 18:11:39 2024 -0700
[MINOR] Update release guide (#11433)
---
release/release_guide.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/release/release_guide.md b/release/release_guide.md
index 0539fc4dd9c..b8dc0595572 100644
--- a/release/release_guide.md
+++ b/release/release_guide.md
@@ -283,9 +283,9 @@ Here is how to go about a bug fix release.
- Create a branch in your repo (<user>/hudi).
- Cherry-pick commits from master that needs to be part of this release. (git
cherry-pick commit-hash). You need to manually resolve the conflicts. For eg, a
file might have been moved to a diff class in master where as in your release
branch, it could be in older place. You need to take a call where to place it.
Similar things like file addition, file deletion, etc.
-- Update the release version by running "mvn versions:set
-DnewVersion=${RELEASE}-rc${RC_NUM}", with "RELEASE" as the version and
"RC_NUM" as the RC number. Make sure the version changes are intended. Then
git commit the changes.
+- Update the release version by running `mvn versions:set
-DnewVersion=${RELEASE_VERSION}-rc${RC_NUM}`, with "RELEASE" as the version and
"RC_NUM" as the RC number. Make sure the version changes are intended. Then
git commit the changes.
- Ensure both compilation and tests are good.
-- I assume you will have apache/hudi as upstream. If not add it as upstream
+- If apache/hudi is not set as upstream, then add it as upstream: `git remote
add upstream https://github.com/apache/hudi.git`
- Once the branch is ready with all commits, go ahead and push your branch to
upstream.
- Go to apache/hudi repo locally and pull this branch. Here after you can work
on this branch and push to origin when need be.
- Do not forget to set the env variables from above section.
@@ -679,4 +679,4 @@ Tweet, post on Facebook, LinkedIn, and other platforms. Ask
other contributors t
It is important that we improve the release processes over time. Once you’ve
finished the release, please take a step back and look what areas of this
process and be improved. Perhaps some part of the process can be simplified.
Perhaps parts of this guide can be clarified.
-If we have specific ideas, please start a discussion on the dev@ mailing list
and/or propose a pull request to update this guide. Thanks!
\ No newline at end of file
+If we have specific ideas, please start a discussion on the dev@ mailing list
and/or propose a pull request to update this guide. Thanks!
