0.20 Feature Release

[rtibbles]

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Beta phase

• Draft upgrade annoucement string
• export strings from Figma into Ditto (feature release only)
• Write update message for translation (feature release only)
• i18n copy writing review for new UI strings (feature release only)
• Translation upload to Crowdin (feature release only)
• QA integration testing
• Bring in new translations
• Final QA pass with translations

Release Candidate (RC) phase

• Write complete release notes and include in release body (but not committed yet)

Release candidate smoke test checklist:

• Debian Installer
• Windows Installer
• Mac App
• Android App
• Raspberry Pi Image
• pex
• kolibri-dev.learningequality.org (BCK)

Release phase

• Changelog (in code) is updated - we do this after the RC phase is complete, so that we can be sure of having a different commit to tag for the final release - Kolibri's version tooling currently does not handle multiple tags on the same commit well.

Release asset smoke test check list (tag specific testers for each item)

• Debian Installer
• Windows Installer
• Mac App
• Android App
• Raspberry Pi Image
• pex
• kolibri-dev.learningequality.org (BCK)
• kolibri-proposed PPA (note that this requires releasing to the PPA currently)

Post release actions

• Unblock release workflow deployment on Github Actions to finalize release
• Release to kolibri PPA
• Update version variable, and date and version text on download page, on Kolibri website
• Release to BCK Prod
• Write and share internal release notes/guidance for comms with details about framing, external vs. internal work, features to highlight. Create and share assets as needed such as feature screencasts
• Merge release to develop
• Share release with team