This is an automated email from the ASF dual-hosted git repository.
ayushtkn pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/hive-site.git
The following commit(s) were added to refs/heads/main by this push:
new 75b04556 HIVE-29090: Update Getting Started and HowToRelease for
removed RELEASE_NOTES and .reviewboardrc (#122)
75b04556 is described below
commit 75b0455660d6315335e585f572bd70b78e9234ca
Author: Hemanth Umashankar
<[email protected]>
AuthorDate: Mon Oct 19 17:38:47 2026 +0530
HIVE-29090: Update Getting Started and HowToRelease for removed
RELEASE_NOTES and .reviewboardrc (#122)
---
content/Development/gettingstarted-latest.md | 2 --
content/community/resources/howtorelease.md | 14 ++++++--------
2 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/content/Development/gettingstarted-latest.md
b/content/Development/gettingstarted-latest.md
index e0712ef4..28d9f6dc 100644
--- a/content/Development/gettingstarted-latest.md
+++ b/content/Development/gettingstarted-latest.md
@@ -66,7 +66,6 @@ To build the current Hive code from the master branch:
LICENSE
NOTICE
README.txt
- RELEASE_NOTES.txt
bin/ (all the shell scripts)
lib/ (required jar files)
conf/ (configuration files)
@@ -101,7 +100,6 @@ Prior to Hive 0.13, Hive was built using [Apache
Ant](http://ant.apache.org/).
LICENSE
NOTICE
README.txt
- RELEASE_NOTES.txt
bin/ (all the shell scripts)
lib/ (required jar files)
conf/ (configuration files)
diff --git a/content/community/resources/howtorelease.md
b/content/community/resources/howtorelease.md
index d260ec52..089f99f1 100644
--- a/content/community/resources/howtorelease.md
+++ b/content/community/resources/howtorelease.md
@@ -202,15 +202,13 @@ mvn versions:set -DnewVersion=0.7.0
-DgenerateBackupPoms=false
Make sure to update the version property in standalone-metastore/pom.xml and
upgrade-acid/pom.xml.
3. Remove the storage-api from the list of modules to build in the top level
pom.xml. Set the storage-api.version property to the release of storage-api
that you are using for your release. Make sure to set the storage-api.version
property in standalone-metastore/pom.xml as well.
-4. Update the the value of the `TRACKING_BRANCH` field in the `.reviewboardrc`
file to point to the `origin/branch-X.Y`.
-5. Verify that the build is working with changes.
-6. Commit these changes with a comment "Preparing for X.Y.Z release".
-7. If not already done, merge desired patches from trunk into the branch and
commit these changes. Avoid usage of "git merge" to avoid too many merge
commits. Either request the committer who committed that patch in master to
commit to this branch, or commit it yourself, or try doing a git cherry-pick
for trivial patches. Specifics of this step can be laid down by the release
manager.
-8. You probably also want to commit a patch (on both trunk and branch) which
updates README.txt to bring it up to date (at a minimum, search+replacing
references to the version number). Also check NOTICE to see if anything needs
to be updated for recent library dependency changes or additions.
+4. Verify that the build is working with changes.
+5. Commit these changes with a comment "Preparing for X.Y.Z release".
+6. If not already done, merge desired patches from trunk into the branch and
commit these changes. Avoid usage of "git merge" to avoid too many merge
commits. Either request the committer who committed that patch in master to
commit to this branch, or commit it yourself, or try doing a git cherry-pick
for trivial patches. Specifics of this step can be laid down by the release
manager.
+7. You probably also want to commit a patch (on both trunk and branch) which
updates README.txt to bring it up to date (at a minimum, search+replacing
references to the version number). Also check NOTICE to see if anything needs
to be updated for recent library dependency changes or additions.
1. Select all of the JIRAs for the current release that aren't FIXED
and do bulk update to clear the 'Fixed Version' field.
- 2. Likewise, use JIRA's [Release
Notes](https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12310843)
link to generate content for the RELEASE_NOTES.txt file. Be sure to select
'Text' format. (It's OK to do this with a direct commit rather than a patch.)
- 3. Update the release notes in trunk with the release notes in branch.
-9. Tag the release candidate (R is the release candidate number, and also
starts from 0):
+ 2. Use JIRA's [Release
Notes](https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12310843)
link to verify and finalize the release notes for version X.Y.Z. These notes
are published from JIRA and linked from the website.
+8. Tag the release candidate (R is the release candidate number, and also
starts from 0):
```
git tag -a release-X.Y.Z-rcR -m "Hive X.Y.Z-rcR release."
