• Needed for branded client X.x.x release (link to branded release ticket)

Patch Release Template

TODO: patch_release_template.md is used for this ticket because it's the newest, updated version for a release ticket template. Check if anything is missing from release_template.md and merge here. So we can use the same template for a patch, minor or major release in future.

• QA: Update Test Plans
• QA: Inform the docu team on rocketchat #documentation-internal about an upcoming major or minor release
• QA: Check the translations coming from https://github.com/owncloud/client/actions/workflows/translate.yml
• QA: Make sure squish tests are running successfully on X.x branch: go to https://github.com/owncloud/client, click on 'commits' above the source tree, click on green checkmark of latest commit, click 'Details' on 'continious-integration/drone/push' and check GUI-tests-@smokeTest
• DEV: Check for new OpenSSL version
• DEV: Check dependencies for updates
• DEV: Prepare the release in a X.x version branch (a patch release is maintained in the minor release branch)
• DEV: bump VERSION.cmake in master to say 2.(x+1).x unless already done.

• DEV: Tag and build builds for theme 'ownCloud' and 'testpilotcloud' (includes ChangeLog for the tag on https://github.com/owncloud/client/releases/)
• QA: Ping #documentation-internal: Changelog is ready. (open doc issues for already known doc-relevant items)
• DEV: Provide 'testpilotcloud' on Beta update channel
• Beta/RC Communication
  • Website links for beta (needed for the following posts)
  • Central post https://central.owncloud.org/tags/c/news/desktop
  • All other stakeholders
• QA: Check Crash reporter (WIN/Mac/Linux Appimage: start 'owncloud --debug' on cmd line, system tray right click menu: 'Crash now - qt fatal')

• DEV: Smash box test Make sure tests run on latest version
• QA: Run automated tests (includes Smoke test)
  • All Linux platform install and gpg test ssh://git@gitea.owncloud.services:2222/client/linux-docker-install.git
    • manually deploy a linux download repo, or use a download repo from https://download.owncloud.com/desktop/ownCloud/testing/
    • in defs.sh edit repo= and update platform_docker_images=
    • RUN.sh -> paste the log/test_YYYYMMDD_hhmm.log file into the client release ticket.
    • TO DO: extend 08-appimage.sh ("xvfb-run")
• QA: Antivirus scan
• QA: Create testplan according to release type (patch release: add tests in a comment, for minor release: create a separate ticket), for testplan templates see https://confluence.owncloud.com/display/OG/Desktop+Client+Release+Process and link here
• QA: Add changelog testing as a comment (to above testplan ticket or here), changeLog issues see https://github.com/owncloud/client/releases/ and link here

• DEV: Tag and build builds for theme 'ownCloud' and 'testpilotcloud' for final build
  • TODO: create confluence page with info about final DEV release steps WIP: Final release steps
• DEV: Adjust Linux Templates to support the next patch release version (e.g. 2.9.1) @dschmidt @fmoc
• DEV: Ping #release-coordination so that marketing can do their actions
• DEV: Create a (draft) release with Download links - save as a draft until smoke tested
• QA: Create a new release issue for a branded release if needed Branded Client Release Template
• QA: Give heads-up before the final release

• QA: Smoke test
• DEV: Publish the release in GitHub
• QA: Check documentation

• Final Marketing and Communication
  • Website links for final release (needed for the following posts)
  • QA: Central post https://central.owncloud.org/tags/c/news/desktop
  • QA: Inform on #updates channel, so that marketing knows about the new release
  • QA: Inform packagers - ping @dragotin (openSUSE)

• QA/DEV: Update stable channel in the owncloud hosted auto updater
• QA: Ensure that the client patch release template is up to date and in sync with other client templates
• QA: Ensure that the client test plan template is up to date.

• DEV: Check the crash reporter for bad/frequent crashes