Skip to content

Releasing a New Version

H. Lehmann edited this page Sep 5, 2020 · 7 revisions

This wiki contains the developer documentation for AntennaPod. If you are a user and you are looking for help, have a look at our website!


Basics

  • Run Unit Tests
  • Smaller changes can just be tested on one device (until release time)
  • When working on something you can't reproduce, upload an apk and ask others to test

One Week Prior to Release

  • Stop making significant changes
  • Upload the source strings (core/values/strings.xml ?) to Transifex
  • Test on physical devices
  • Test on emulators (one each of 2.3, 4.x and 5.0)
  • Upload apk to dropbox and create an issue for the upcoming release, requesting people to test
  • Save app/build/outputs/mapping/release/mapping.txt so we can decode crashes as reported on Google play
  • What to do about Flattr API Keys?

Source

From #604 (but ideally we'll clean this up as we go through the process)

@TomHennen When commiting smaller changes, i usually only tested them on my personal device. When i was working on a larger feature or a device-specific bug that i could not reproduce, i uploaded an APK and asked other people to test it. I have also always uploaded a new build of the develop branch after each commit.

About one week before each release, i usually stopped making any significant changes to the code, uploaded the source strings to transifex for translation and tested the upcoming version on two physical devices and a couple of emulators. Most of the time, i only tested the new version on Android 2.3, one 4.x device and one 5.0 device. Many of the compatibility issues that have been reported to me were device-specific and couldn't be reproduced on the emulator. So it is also a good idea to open an issue like this before a major release and ask people to test a preview version and give feedback.

There are also some unit tests, but they don't cover everything. The UI tests haven't been working since the Android support library got the material design update. But fixing these UI tests could save you some time because a lot of workflows like adding a feed, playing a file or switching from one list to the other are already implemented.