Release data_exporter 0.2.1

Reason

needs a release because of the fix merged in PR

That is a latent bug that would only be noticed by users if they are using settings that enabled/disable apps by groups. In "ordinary" system installations, the bug is not noticeable.

When core 10.11 is released, new core code will make the bug very noticeable. So the app release should be done and available before core 10.11 is released.

The app still works fine with older core versions - the core min-version does not need to be changed.

Product approval

[ ] Verify transifex commits are in master: If a folder https://github.com/owncloud//tree/master/l10n exists, then https://drone.owncloud.com/owncloud/ should receive nightly '[tx] updated from transifex` ...
[ ] Ping pmaier to check info.xml description and screenshot
[ ] Get approval on translations from pmaier - send the date of the last tx commit from drone to Patrick

QA

[ ] Create QA Milestone and set the description to $version
[ ] Move tickets from milestone development to qa (testplan and tickets mentioned in release ticket)
[x] Create release branch with the format "release-$version"
[x] Create "$version Testplan" (QA templates or Enterprise) -> #208
[ ] copy new/reopened issues from the previous release ticket as 'Issues to review' below.
[ ] check if Non-normal Release Process applies, and adapt this checklist.

Documentation

[ ] Changes in the docs needed? If so create issue in owncloud/docs-server.

Marketing

[ ] Ping @owncloud/marketing
[ ] Update https://confluence.owncloud.com/display/PROD/Upcoming+Releases
[ ] Request a screenshot if the app is new or changed fundamentally

Build

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

[x] Bump version in info.xml (no version suffix)
[x] Bump "sonar.projectVersion=" in sonar-project.properties (no version suffix)
[ ] Check php version dependency in info.xml
[x] Check minimum ownCloud version dependency in info.xml
[x] Change CHANGELOG.md 'Unreleased' to '$version' (today's date)

Beta/RC

[ ] Ping product owner to create github tag for v${version}-rc1 on release branch (see https://confluence.owncloud.com/display/EN/Product+Owners+List)
[x] Build and sign RC tarball from github tag v${version}-rc1 (see handbook for how to build)
[x] Upload as Github release using changelog entries
[ ] Test and document in testplan + manual explorative testing:
- [ ] If this is an enterprise app: Enabling the app must start the grace period
- [x] Add section "Changlog Testing" using github releases text or CHANGELOG.md from release branch
- [ ] Do changelog tests
- [ ] Do regression tests
- [ ] => Final "Go" from QA (set 'QA-ready' label) => else do another RC after fixing issues in the "release-$version" branch

Final

[x] Check that no documentation issues are pending
[x] Rename last RC tarball to final
[x] Create github tag for final v${version} on release branch
[x] Upload as Github release using changelog entries

Publishing

[ ] ~Upload tarball to marketplace (see handbook in confluence for details)~
[ ] ~Publish tarball for customers - old 10, old 10.0 and new portal (see handbook for details)~
[x] Send mail to release-coordination with link to this ticket and to the changelog
[x] Copy email to rocket chat #updates channel

Post-release

[x] Add a new 'Unreleased' section in CHANGELOG.md (and also update links at the bottom!)
[x] Create PR to merge changes back to the master branch with description "Closes #XYZ" with the release ticket number
[x] Rename QA milestone to $version and close the milestone
[x] Update https://confluence.owncloud.com/display/PROD/Upcoming+Releases
[x] Ensure release template is up to date
[x] Ensure the testplan template (community or enterprise) is up to date
[x] Close the testplan issue

owncloud / data_exporter