Release documentation

How to release the app

create a new release branch with the name release_<next_version_number>
increase the version number to <next_version_number>
- in https://github.com/Plant-for-the-Planet-org/treecounter-app/blob/staging/package.json for the JavaScript-Code
- in https://github.com/Plant-for-the-Planet-org/treecounter-app/blob/staging/android/app/build.gradle for the Android app - also increase the versionCode to the next number
- in https://github.com/Plant-for-the-Planet-org/treecounter-app/blob/staging/ios/TreecounterApp/Info.plist for the iOS app - you can also increase the bundle version to the next number
commit the increase of the version number with a suitable message

use Android Studio with the menu Build->Generate Signed Bundle/APK to generate signed APKs
- this results into five APK files for different architectures
- we omit the universal APK and only upload the other four APK into Google Play Store Console as the universal binary would be marked as redundant by Google
create a new Alpha, Beta or Production release in the Google Play Store console
- upload the four APK mentioned above
- add a release note
- publish the release

Use menu Product->Archive to create a new archive for releasing the app
- use the Organizer to distribute the app (method iOS App Store) to App Store Connect
- wait for the build to be processed by Apple
for TestFlight the processed build has to be activated by added a declaration (TODO: how is the name?)
for distribution a new version with <next_version_number> has to be created
- choose the processed build for this version
- add a release note
- push the release into the review process with automatic release

Merge the release branch into the master branch. This should be done anyway after the release is completed.

Run the script ./upload-native-source-maps.sh (in the app repository) to upload source maps to Bugsnag for the native client.
Source maps for the web client will be uploaded automatically within the CircleCI build of the master branch.