Next feature release

See original GitHub issue

I started collecting issues to be solved until we can merge master to release to prepare the next feature release and/or beta version.

I think we can do this step as soon as the known problems around the “new dir” implementation are fixed or considered not to be critical. The following issues are currently open:

Link to open issues for NewDir I set prio labels for these issues based on my personal opinion about their importance.

Edit: Release is ongoing. Checklist added:

Check/Import incoming Translations from Crowdin
Check/Insert correct version name as headline in changelog-release.xml
Build release on CI server
Perform smoke test with resulting cgeo-release.apk before continuing
Upload and publish cgeo-release.apk to Google Play to 50% of users (staged release)
Tag the release on Github
Publish the release on Github including upload of cgeo-release.apk to Github
Rename/Create milestones on Github
Regularly check Google Play crash reports, support mail, etc. and react accordingly
Go/NoGo decision

In case of Go:

Increase publish percentage to 100%
Publish release on F-Droid
Trigger notification to status.cgeo.org via CI server a few hours after increasing the publish percentage
Post release info to Facebook
Post release info to G+
Post release info to Twitter (via @SammysHP)
#6413 should be done after publishing the release
Merge changes to FAQ https://github.com/cgeo/cgeo.github.io/pull/136