Skip to content

Latest commit

 

History

History
95 lines (74 loc) · 6.84 KB

release_template.md

File metadata and controls

95 lines (74 loc) · 6.84 KB
Raw

Reason

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

Template

Release Template

TODO:

  • Check if anything is missing from release_template_outdated_2020.md and merge here. We use the same template for a patch, minor or major release now.
  • For each item add a link to the respective action if available

Administration

  • QA: Update Test Plans
  • Update supported platforms @michaelstingl
  • QA: Check the translations coming from transifex: https://github.com/owncloud/client/commits/ -> Filter based on a release branch/tag and search for [tx] updated client translations from transifex [skip ci]
  • DEV: Check for new OpenSSL version
  • DEV: Update dependencies
  • DEV: For a major release create X version branch
    • QA: In drone adjust the branch for nightly GUI tests @individual-it
  • QA: Communicate documentation changes
    • Inform #documentation-internal (@mmattel) about the start of testing phase (latest a week before the release!). They'll prepare a PR with respective doc version
    • Open issues in docs-client-desktop repo for already known doc-relevant items and mark them accordingly, e.g. backport to 2.X.x necessary
  • Decide if the prerelease stage will be public or internal @michaelstingl
  • Announce feature freeze in #release_coordination channel before Beta build
  • Announce string freeze in #release_coordination channel a few days later
    • Inform #documentation-internal about it so that they can do the translations

Copy for Each Build (Beta/RC)

QA

  • QA: Antivirus scan the first RC
  • QA: Upload linux gpg keys to key server
  • QA: Check Crash reporter: start 'owncloud --debug' on cmd line, system tray right click menu: 'Crash now - qt fatal' -> report window not empty, sending the report works)
    • Windows
    • macOS
    • AppImage (Linux)
  • Automated tests (for the first beta and the last RC):
  • Manual tests:
    • QA: Changelog test
    • QA: Regression test
    • QA: Branded regression test

Prerequisites for final release

  • DEV: Create vX.Y.Z release tag in client repo and everywhere else
  • DEV: bump VERSION.cmake in master to say 3.(x+1).x unless already done.

Final Rebuild after QA Approval

  • QA: Inform on #documentation-internal that the tag for the final release will be set a day or at least half a day before (only for a major/minor release). They'll merge docs PR before that.
  • DEV: Create final release tag (e.g., v4.5.6)
  • DEV: Create builds for themes 'ownCloud' and 'testpilotcloud' for final release tag
  • DEV: Update version for future builds
  • QA: Check squish tests running successfuly on drone for the final tag v3.X.x
  • QA: Create a new release issue for a branded release if needed Branded Client Release Template

Final Steps

  • QA: Smoke test
  • DEV: Publish the release in GitHub
  • QA: Update lines 4 and 5 of install docs with the final build number. Merge into master and backport to the respective branch
  • QA: Check that documentation offers the new version
  • DEV: Merge version branch into master
  • DEV: Update SBOM

Marketing and Communication

Infrastructure Check

  • QA/DEV: Update stable channel in the owncloud hosted auto updater
  • QA: Check the linux download pages whether the URLs are correct (e.g. contain stable, not testing)
  • QA: Ensure that the client release template is up to date

A Few Days After the Release