Castopod
/
AntennaPod
mirror of https://github.com/AntennaPod/AntennaPod.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

making it more organized, more specifics needed

Tom Hennen 2015-02-23 19:54:22 -05:00
parent a305ea5248
commit d54a46c6c3
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
Releasing-a-New-Version.md

@ -1,3 +1,17 @@
## 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](https://www.transifex.com/projects/p/antennapod/)
* 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
* What to do about Flattr API Keys?
## Source
From [#604](../issues/604) (but ideally we'll clean this up as we go through the process) From [#604](../issues/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. >@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.