REMINDER: Please add your name to the checkbox when you have completed an item

Reason

• Migrate app out of owncloud/core repository

Open Tasks

• code parity Check code alignment #118
• translations Setup Transifex #136

QA

• Create QA Milestone and set the description to $version @patrickjahns
• Move items from development to qa @patrickjahns
• Create release branch with the format "release-$version" @patrickjahns
• Create "1.4.0 Testplan" @davitol Tracking testing results for encryption #142

Documentation

• Changes in the docs needed?

Marketing

• Ping @owncloud/marketing
• Check/adapt info.xml stuff
• Check/adapt screenshot
• Blog post or other communication if applicable

Build

All actions to be done on the release branch from here:

• Bump version in info.xml (no version suffix) @patrickjahns
• Update CHANGELOG.md - Change CHANGELOG.md 'Unreleased' to '$version' (final release date unknown) @patrickjahns

Beta/RC

• Create github tag for 'v${version}RC1' on release branch @patrickjahns
• Build and sign RC tarball from github tag 'v${version}RC1' (see
  handbook for how to build) @patrickjahns
• Upload as Github release using changelog entries @patrickjahns
• Test and document in testplan => Final "Go" from QA (set 'QA-ready' label) => else do another RC after fixing issues in the "release-$version" branch @davitol Tracking testing results for encryption #142

Final

• Create github tag for final 'v${version}' on release branch
• Build and sign final tarball from github tag 'v${version}' (see
  handbook for how to build)
• Upload as Github release using changelog entries
• Smoke test tarball (at least install + enable)

Publishing

• Upload tarball to marketplace (see handbook for details) app will not be individually published
• Publish tarball for customers (see handbook for details) app will not be individually published
• Send mail to release-coordination with link to this ticket and to the changelog app will not be individually published

Post-release

• Rename QA milestone to '$version'
• Add a new 'Unreleased' section in CHANGELOG.md and add release date '$version - $currentDate' (ex: 3.1.5 - 2018-08-01)
• Create PR to merge changes back to the master branch with
  description "Closes #XYZ" with the release ticket number