@@ -10,18 +10,20 @@ This is the process to use to do a release:
10
10
libraries' versions, and making sure that the project version in the ` gradle.properties ` file is
11
11
correctly set to the next planned release version.
12
12
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.
16
16
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
19
19
and will appear in maven with in a day or two at most (typically a few hours).
20
20
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
22
25
version. This PR can and probably should also include updating any documentation (CHANGELOG.md,
23
26
README.md, etc) that mentions the previous version. Make sure the badge in the top README.md
24
27
reflects the accurate upstream otel version.
25
28
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
0 commit comments