Skip to content

Commit

Permalink
Changing release branch to main branch
Browse files Browse the repository at this point in the history
  • Loading branch information
dvernon-splunk committed Oct 24, 2023
1 parent 9fe533b commit 7a8dfa5
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion RELEASING.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
How to release splunk-otel-ios:

* Make sure to bump the release version on both SplunkRum.swift and Podfile
* Create a release branch named “release-X.X.X” filling in X with the next release version. Ensure that this branch builds correctly.
* Build the main branch locally to ensure it builds correctly and all unit tests are passing.
* Run splunk-otel-ios-crashreporting locally, making sure that the dependency points to the main branch to be released. If necessary, fix any breaking issues before releasing a new version of splunk-otel-ios. Follow the following steps with splunk-otel-ios-crashreporting as well.
* Create a signed tag with `git tag -s X.X.X` filling in X with the next release version. Push this tag to the repo. You can also use Github's release flow, which will automatically sign the tag as well.
* In github, go to the releases section on the right and click the Releases header. Then click “Draft a New Release.” Choose the tag you just created (or create a new one here) and fill in release notes.
Expand Down

0 comments on commit 7a8dfa5

Please sign in to comment.