Skip to content

Release 7.1.0 #12549

@ishabaral

Description

@ishabaral

Administration

  • QA: Update Test Plans
  • Update supported platforms @DeepDiver1975
  • 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: Communicate documentation changes
    • Inform documentation team 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 @DeepDiver1975

Copy for Each Build (Beta/RC)

  • DEV: Tag (Beta or RC) and build builds for theme 'ownCloud' and 'testpilotcloud'
  • QA: Smoke test @ishabaral
  • DEV: GitHub release
  • Beta/RC Communication
  • DEV: Prepare the update server for new version (AppImages included)
    • DEV: Provide 'testpilotcloud' on Beta update channel

QA

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 X.(Y+1).Z unless already done.

Final Rebuild after QA Approval

  • QA: Inform documentation team 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., vX.Y.Z)
  • DEV: Create builds for themes 'ownCloud' and 'testpilotcloud' for final release tag
  • DEV: Update version for future builds
  • QA: Check squish tests running successfully on drone for the final tag vX.Y.Z
  • 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions