Skip to content

Commit 1543815

Browse files
authored
Bump gradle.properties version in 1.9.0 (#1096)
* bump version * update release notes * added more instructions * spotless apply
1 parent 8d4333c commit 1543815

File tree

2 files changed

+11
-9
lines changed

2 files changed

+11
-9
lines changed

RELEASING.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -10,18 +10,20 @@ This is the process to use to do a release:
1010
libraries' versions, and making sure that the project version in the `gradle.properties` file is
1111
correctly set to the next planned release version.
1212

13-
2) Run the `scripts/tag-release.sh` script to create and push a signed release tag. Note that it
14-
assumes that the remote is named `origin`, if you named yours differently you might have to push
15-
the tag manually.
13+
2) Run the `scripts/tag-release.sh` script with latest release version number,
14+
eg: ./tag-release.sh 1.2.3 to create and push a signed release tag. Note that it assumes that the
15+
remote is named `origin`, if you named yours differently you might have to push the tag manually.
1616

17-
3) Wait for gitlab to run the release job. If all goes well, it will automatically close
18-
and release the "staging" repository...which means the build has been published to sonatype
17+
3) Wait for gitlab android-releaser to run the release job. If all goes well, it will automatically
18+
close and release the "staging" repository...which means the build has been published to sonatype
1919
and will appear in maven with in a day or two at most (typically a few hours).
2020

21-
4) Create a PR to update the version in the `gradle.properties` to the next development
21+
4) Once this PR is merged, create a release in Github that points at the newly created version,
22+
and make sure to provide release notes that at least mirror the contents of the CHANGELOG.md
23+
24+
5) Create a PR to update the version in the `gradle.properties` to the next development
2225
version. This PR can and probably should also include updating any documentation (CHANGELOG.md,
2326
README.md, etc) that mentions the previous version. Make sure the badge in the top README.md
2427
reflects the accurate upstream otel version.
2528

26-
5) Once this PR is merged, create a release in Github that points at the newly created version,
27-
and make sure to provide release notes that at least mirror the contents of the CHANGELOG.md
29+
6) Go to Slack and notify relevant about release

gradle.properties

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,5 +17,5 @@ org.gradle.jvmargs=-Xmx2048m -Dfile.encoding=UTF-8
1717
android.useAndroidX=true
1818

1919
# generate the BuildConfig class that contains the app version
20-
version=1.8.0
20+
version=1.9.0
2121
group=com.splunk

0 commit comments

Comments
 (0)