From 154381519950b4ea4cbeabf1f598687e3497d233 Mon Sep 17 00:00:00 2001
From: tonzhan2 <140451394+tonzhan2@users.noreply.github.com>
Date: Fri, 6 Dec 2024 12:02:21 +1300
Subject: [PATCH] Bump gradle.properties version in 1.9.0 (#1096)

* bump version

* update release notes

* added more instructions

* spotless apply
---
 RELEASING.md      | 18 ++++++++++--------
 gradle.properties |  2 +-
 2 files changed, 11 insertions(+), 9 deletions(-)

diff --git a/RELEASING.md b/RELEASING.md
index bd121f5a..5ab8303a 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -10,18 +10,20 @@ This is the process to use to do a release:
    libraries' versions, and making sure that the project version in the `gradle.properties` file is
    correctly set to the next planned release version.
 
-2) Run the `scripts/tag-release.sh` script to create and push a signed release tag. Note that it
-   assumes that the remote is named `origin`, if you named yours differently you might have to push
-   the tag manually.
+2) Run the `scripts/tag-release.sh` script with latest release version number,
+   eg: ./tag-release.sh 1.2.3 to create and push a signed release tag. Note that it assumes that the
+   remote is named `origin`, if you named yours differently you might have to push the tag manually.
 
-3) Wait for gitlab to run the release job. If all goes well, it will automatically close
-   and release the "staging" repository...which means the build has been published to sonatype
+3) Wait for gitlab android-releaser to run the release job. If all goes well, it will automatically
+   close and release the "staging" repository...which means the build has been published to sonatype
    and will appear in maven with in a day or two at most (typically a few hours).
 
-4) Create a PR to update the version in the `gradle.properties` to the next development
+4) Once this PR is merged, create a release in Github that points at the newly created version,
+   and make sure to provide release notes that at least mirror the contents of the CHANGELOG.md
+
+5) Create a PR to update the version in the `gradle.properties` to the next development
    version. This PR can and probably should also include updating any documentation (CHANGELOG.md,
    README.md, etc) that mentions the previous version. Make sure the badge in the top README.md
    reflects the accurate upstream otel version.
 
-5) Once this PR is merged, create a release in Github that points at the newly created version,
-   and make sure to provide release notes that at least mirror the contents of the CHANGELOG.md
+6) Go to Slack and notify relevant about release
diff --git a/gradle.properties b/gradle.properties
index 73fdecd6..2cccaebd 100644
--- a/gradle.properties
+++ b/gradle.properties
@@ -17,5 +17,5 @@ org.gradle.jvmargs=-Xmx2048m -Dfile.encoding=UTF-8
 android.useAndroidX=true
 
 # generate the BuildConfig class that contains the app version
-version=1.8.0
+version=1.9.0
 group=com.splunk