TOTP 0.6.0

[PVince81]

Reason

• Release needed for add validate api for totp #38
• other topics ? check changelog

QA

• Create QA Milestone
• Move items from development to qa
• Create release branch with the format "release-$version" https://github.com/owncloud/twofactor_totp/tree/release-0.6.0 @davitol
• Create "0.6.0 Testplan" Tracking testing results for twofactor_totp 0.6.0 #128 @davitol

Documentation

• Changes in the docs needed? Document twofactor_totp key validation OCS API docs#674

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) @davitol
• Update CHANGELOG.md - Change CHANGELOG.md 'Unreleased' to '$version' (final release date unknown) @davitol

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

Final

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

Publishing

• Upload tarball to marketplace (see handbook for details) @patrickjahns
• Publish tarball for customers (see handbook for details) @patrickjahns
• Send mail to release-coordination with link to this ticket and to the changelog @patrickjahns

Post-release

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

[micbar]

Seems like DEV is done, PR merged.

[davitol]

@micbar @patrickjahns RC1 Tarball is QA-ready. No new issues found:

Results here: #128