Releases

Latest Release

F-Droid Links

• Repository page: https://f-droid.org/en/packages/com.forrestguice.suntimeswidget/
• Technical info: https://f-droid.org/wiki/page/com.forrestguice.suntimeswidget
• Build Metadata: https://gitlab.com/fdroid/fdroiddata/blob/master/metadata/com.forrestguice.suntimeswidget.txt
• Last Build: https://f-droid.org/wiki/index.php?title=com.forrestguice.suntimeswidget/lastbuild&redirect=no
• F-Droid Status page: https://f-droid.org/wiki/page/Main_Page

---

Procedural Stuff

Release Cycle

There isn't a 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)

To Cut a Release

1. create a release branch (prep-release-v#).
2. increment versionCode and versionName; commit.
3. run lint: fix major errors/warnings; commit.
4. build w/ cmd line: gradlew build; confirm the build completes without errors (lintVitalRelease succeeds).
5. build w/ fdroidserver using the most recent commit; confirm the build completes without errors.
6. 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 3, 4, 5, and 6 until happy).
7. create a pull request; merge prep-release into master (and cleanup / delete it).
8. draft a new release; browse the tracker / commit history and add a note summarizing each issue (or major commit).
9. publish the release; each release is tagged with v<major>.<minor>.<patch>.
10. attach signatures to download artifacts (https://wiki.debian.org/Creating%20signed%20GitHub%20releases)
11. 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).