Release Checklist

For building a new release of Piwigo-Android we want to follow those steps:

Beta release

• check all issues associated with the next milestone
• drop summary of changes since last revision into a file called whatsnew (not yet done so far)
• check for needed updates in the privacy policy
• merge latest translations (not yet done so far)
• notify translators and ask for updates on crowdin (not yet done so far)
• update versionCode and versionName in app/build.gradle (to an odd version code and a '-beta' suffix)
• check for needed updates in User Guide
• create new screenshots (not yet done so far)
• update translations in crowdin (what we can translate ourselves)
• create a tag git tag vX.Y.Z-beta git push origin vX.Y.Z-beta (beta versions will not be included in f-droid)
• build/Generate Signed AAB (and publish it to GPlay on the beta-track) by ./gradlew bundleRelease
• notify testers and ask them to test (not done so far)
• wait 7-14 days for feedback, new translations and new bugs

Final release

• fix newly reported bugs
• check for needed updates in the privacy policy
• merge new translations
• close the milestone on github
• update versionCode and versionName in app/build.gradle (to an even version code and no '-beta' suffix)
• create new screenshots (if relevant translations done - not yet done so far)
• create a tag git tag vX.Y.Z git push origin vX.Y.Z (this tag will automatically trigger inclusion in f-droid)
• create release notes from github tag
• build/Generate Signed AAB (and publish it to GPlay on the release-track) by ./gradlew bundleRelease
• create a new milestone for a new release after the latest currently planned one
• update versionCode and versionName in app/build.gradle (to an odd version code and a '-dev' suffix)
• review the issues linked to the next milestone, put a tentative deadline to the milestone
• assign issues of the next release to developers and get started with what is left