Created Releasing a New Version (markdown)

Tom Hennen 2015-02-23 19:16:28 -05:00
parent fd31f76191
commit 9536ae0d1c

@ -0,0 +1,6 @@
From #604
>@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.