Release richdocuments 4.1.0

[jnweiger]

Using issue template from /home/testy/src/github/owncloud/QA/tools/release/templates/server_app_release_template.md
This is the server app release template, please copy the part below in a new ticket.
For instructions around app releases, see https://confluence.owncloud.com/display/OG/Releasing+Apps

Reason

• Zotero integration + refactor and bug fixes of admin/personal panel #505
• Bugfix: broken version revision #522
• fix: drop usage of ${} #520

Product approval

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

QA

• Create QA Milestone and set the description to $version
• Move tickets from milestone development to qa (testplan and tickets mentioned in release ticket)
• Create release branch with the format "release-$version"
• Create "$version Testplan" (QA templates or Enterprise) -> [QA] richdocuments 4.1.0 Testplan #526
• 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 . -> Maybe extend Collabora / Richdocuments documentation? docs-server#1170

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 (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 (see https://confluence.owncloud.com/display/EN/Product+Owners+List)
• Build and sign RC tarball from github tag v${version}-rc.1 (see handbook for how to build)
• Check buildlog for security reports
• 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.
  • PHP 7.3 compatibility (HCLOUD_SERVER_IMAGE=debian-10 OC10_VERSION=10.11 oc10.sh ...)
  • => 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 (see handbook in confluence for details)
• 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
• Copy email to rocket chat #updates channel

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://confluence.owncloud.com/display/PROD/Upcoming+Releases
• Ensure release template is up to date
• Ensure the testplan template (community or enterprise) is up to date
• Close the testplan issue

[jnweiger]

https://github.com/owncloud/richdocuments/releases/download/v4.1.0-rc.1/richdocuments-4.1.0-rc.1.tar.gz

[jnweiger]

Issues seen while testing

• Richdocuments complains about incorrect zotero api key #527 -> blocker candidate
• Zotero private key is exposed in the web UI #528

[mrow4a]

@jnweiger fix for #521 is also in 4.1.0rc , as reported by one of the customers