Releases

Latest Release

There isn't a set release cycle, but commits to master should be tagged early and often. For this project that means:

at least once a month
at most once a week
no more than once per F-Droid checkupdate cycle (https://f-droid.org/wiki/page/checkupdates)

create a release branch (prep-release-v#).
increment versionCode and versionName; commit.
update the changelog; add versionName and releaseDate; commit;
run lint: fix major errors/warnings; commit.
build w/ cmd line: gradlew build; confirm the build completes without errors (lintVitalRelease succeeds).
install and test the signed release apk on an actual device.
- if there's a bug.. fix it on the master branch, sync the prep-release branch, and retest the build (repeat 4, 5, and 6 until happy).
create a pull request; merge prep-release into master (and cleanup / delete it).
draft a new release; in the release notes summarize the major entries to the changelog (highlights only).
publish the release; each release is tagged with v<major>.<minor>.<patch>.
wait for fdroid to detect the new release; monitor the fdroid wiki page for build errors (https://f-droid.org/wiki/index.php?title=com.forrestguice.suntimeswidget/lastbuild&redirect=no).
(optional) create a signed release apk (using your personal developer key); update the release.
(optional) if creating a signed release apk, attach your GPG signature to ALL download artifacts (https://wiki.debian.org/Creating%20signed%20GitHub%20releases); update the release.

Connect a device/emulator to adb. adb devices
Run the SuntimesScreenshots instrumentation test: gradlew connectedAndroidTest -Pandroid.testInstrumentationRunnerArguments.class='com.forrestguice.suntimeswidget.SuntimesScreenshots'
Copy files from the device. adb pull sdcard/Android/data/com.forrestguice.suntimeswidget/files/Pictures/test-screenshots/<version>/<locale>
Upload select files to gh-pages branch; see https://gist.github.com/joncardasis/e6494afd538a400722545163eb2e1fa5.

Useful Resources