notes 2.0.7 release

[jnweiger]

This is the server app release template, please copy the part below in a new ticket.
For instructions around app releases, see https://kiteworks.atlassian.net/wiki/spaces/OG/pages/404326697/Releasing+Apps

Reason

• Release needed for fix: ensure that notes are not stored inside a shared folder #488
• Javascript dependency updates:
  • Bump gulp-ng-annotate from 1.1.0 to 2.1.0 in /js #398
  • Bump gulp-uglify from 1.5.4 to 3.0.2 in /js #399
  • Bump karma 0.13.3 to 6.3.4 #403
  • Bump karma-jasmine 0.3.6 to 4.0.1 #402
  • Bump karma 0.13.3 to 6.3.4 #403
• Dropped support for PHP 7.2 in [tests-only] Update drone starlark and drop PHP 7.2 #404

Product approval

• Verify transifex commits (enterprise should update weekly, others daily): If folder l10n exists, then git log should show '[tx] updated from transifex` ...
• Check info.xml description and screenshot

QA

• Create QA Milestone and set the description to $version
• Create release branch with the format "release-$version"
• Create "2.0.6 Testplan" --> [QA] 2.0.7 Testplan #489 (QA templates or Enterprise)
• 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 https://github.com/owncloud/docs-server/issues/new .

Marketing

• Update https://kiteworks.atlassian.net/wiki/spaces/PROD/pages/403801090/Upcoming+Releases
• Check for any left over TODO's at https://kiteworks.monday.com/my_work (hide [x] done, empty)

Build

All actions to be done on the release branch (git pull; git checkout -b release-x.x.x) from here:

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

Beta/RC

• git tag -s v${version}-rc.1 on release branch
• Build and sign RC tarball from github tag v${version}-rc.1 (see handbook for how to build)
• Check buildlog for security reports #492
• Check github security tab dependabot reports
  • -> if critical or high entries are reported: open a release blocker issue.
• 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
  • Add section "Changlog Testing" using github releases text or CHANGELOG.md from release branch
  • Do changelog tests
  • Do regression tests
  • Watch out for untranslated strings when locale is de oder de_DE.
  • => Final "Go" from QA (set 'QA-ready' label) => else do another RC after fixing issues in the "release-$version" branch

Final

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

Publishing

• Upload tarball to marketplace (details https://kiteworks.atlassian.net/wiki/spaces/OG/pages/404326697/Releasing+Apps)
• Publish tarball for customers github/owncloud/QA/tools/portal_upload_app.sh - old 10, old 10.0 and new portal (details https://kiteworks.atlassian.net/wiki/spaces/OG/pages/404326697/Releasing+Apps)
• Send mail to release-coordination with link to this ticket and to the changelog github/owncloud/QA/tools/release/oc_release.sh app:status
• Submit mail-text as a Markting Request via https://kiteworks.monday.com/boards/5983659465/views/130504071 using login name + password, (not SSO)
  • Prompt: convert into 5 lines of enduser friendly marketing language, nothing exciting, no exclamation marks, this release is a minor update only:
  • paste email text, review and edit result.

Post-release

• Add a new 'Unreleased' section in CHANGELOG.md (and also update links at the bottom!)
• Create PR to merge changes back to the master branch with description "Closes #XYZ" with the release ticket number
• Rename QA milestone to $version and close the milestone
• Update https://kiteworks.atlassian.net/wiki/spaces/PROD/pages/403801090/Upcoming+Releases
• Ensure release template is up to date
• Ensure the testplan template (community or enterprise) is up to date
• Close the testplan issue
• Check for any left over TODO's at https://kiteworks.monday.com/my_work (hide [x] done, empty)

[jnweiger]

Advancing to 2.0.7, as marketplace saw a 2.0.6 in 2019 🙈

[jnweiger]

Skipped customer communication. I'ts a community app.