From d54a46c6c32631129f8402592d53f23365767ef8 Mon Sep 17 00:00:00 2001 From: Tom Hennen Date: Mon, 23 Feb 2015 19:54:22 -0500 Subject: [PATCH] making it more organized, more specifics needed --- Releasing-a-New-Version.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/Releasing-a-New-Version.md b/Releasing-a-New-Version.md index 8666693..f689190 100644 --- a/Releasing-a-New-Version.md +++ b/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) >@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.