DeepDiver1975 commented 3 years ago

Release 0.6.2

Implement UI and client handling for CSV import https://github.com/owncloud/customgroups/pull/415
Use relative URLs instead of absolute URLs in Notifications https://github.com/owncloud/customgroups/pull/419

[x] 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

[x] Create QA Milestone and set the description to $version
[x] 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) -> #438
[ ] copy new/reopened issues from the previous release ticket as 'Issues to review' below.
[x] check if Non-normal Release Process applies, and adapt this checklist.

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

[x] 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
[x] Manual explorative testing:
- [x] If this is an enterprise app: Enabling the app must start the grace period
- [x] If this is the initial release of an app: Check that the minimum version constraint resolves correctly
- [x] Changelog testing
- [x] Changelog item #415 tested
- [x] Changelog item #419 tested
- [x] 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

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

[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