Skip to content

Latest commit

 

History

History
136 lines (112 loc) · 7.2 KB

File metadata and controls

136 lines (112 loc) · 7.2 KB
name Release
about List of checklist to accomplish for the ownCloud team to finish the release process
title [RELEASE]
labels Release
assignees

Open release

TASKS:

  • [COM] Ping @mmattel about the new release
  • [GIT] Create branch release/M.m.p in owncloud/android from master
  • [DEV] Update version number and name in build.gradle in owncloudApp module
  • [DOC] Update SBOM
  • [DIS] Move Calens files from unreleased to a new folder like M.m.p_YYYY-MM-DD inside the changelog folder
  • [DEV] Check and reorder release notes in ReleaseNotesViewModel.kt to assure nothing important is missing there
  • [DEV] Code review
  • [DIS] Generate final bundle and APK from last commit in release branch
  • [COM] Prepare post in central.owncloud.org (Category:News + Tag:android)
  • [DIS] Check for new screenshots in Play Store/GitHub/F-Droid and generate them
  • [QA] Design test plan
  • [QA] Regression test execution
  • [QA] QA approval
  • [DIS] Upload release APK and bundle to internal ownCloud instance
  • [COM] Ping @mmattel that we are close to sign the new tags
  • [DIS] Upload and publish release bundle and changelog in Play Store
  • [DIS] Update screenshots in Play Store/GitHub/F-Droid
  • [GIT] Create and sign tag vM.m.p in HEAD commit of release branch, in owncloud/android
  • [GIT] Move tag latest pointing the same commit as the release commit
  • [DIS] Publish a new release in owncloud/android
  • [DIS] Release published in Play Store
  • [COM] Publish post in central.owncloud.org (Category:News + Tag:android)
  • [COM] Inform in "ownCloud General" and #general that release is out
  • [GIT] Merge master into release/M.m.p, fixing all the conflicts that could happen, in owncloud/android
  • [GIT] Merge without rebasing release/M.m.p branch into master, in owncloud/android
  • [COM] Ping @DeepDiver1975 to update release information in https://owncloud.com/mobile-apps/
  • [DOC] Update documentation with new stuff by creating issue

QA

Regression test:

Bugs & improvements:

  • (1) ...

Patch release

TASKS:

  • [GIT] Create branch release/M.m.p in owncloud/android from latest
  • [DEV] Update version number and name in build.gradle in owncloudApp module
  • [DOC] Update SBOM
  • [DIS] Update release notes in app and changelog in unreleased with the proper content for the release
  • [DIS] Move Calens files from unreleased to a new folder like M.m.p_YYYY-MM-DD inside the changelog folder
  • [DIS] Copy the unreleased folder in master branch into this branch, to avoid Calens conflicts problems
  • [DEV] Check and reorder release notes in ReleaseNotesViewModel.kt to assure nothing important is missing there
  • [DEV] Code review
  • [DIS] Generate final bundle and APK from last commit in the release branch
  • [DIS] Check for new screenshots in Play Store/GitHub/F-Droid and generate them
  • [QA] Design test plan
  • [QA] Test execution
  • [QA] Trigger BitRise builds for unit tests and UI tests, in case changelog conflicts avoid them in GitHub
  • [QA] QA approval
  • [DIS] Upload release APK and bundle to internal ownCloud instance
  • [DIS] Upload and publish release bundle and changelog in Play Store
  • [DIS] Update screenshots in Play Store/GitHub/F-Droid
  • [GIT] Create and sign tag vM.m.p in HEAD commit of release branch, in owncloud/android
  • [GIT] Move tag latest pointing the same commit as the release commit
  • [DIS] Publish a new release in owncloud/android
  • [DIS] Release published in Play Store
  • [COM] Inform in "ownCloud General" and #general that release is out
  • [GIT] Merge master into release/M.m.p, fixing all the conflicts that could happen, in owncloud/android
  • [GIT] Merge without rebasing release/M.m.p branch into master, in owncloud/android
  • [COM] Ping @DeepDiver1975 to update release information in https://owncloud.com/mobile-apps/

QA

QA checks:

  • Smoke test
  • Upgrade test

Bugs & improvements:

  • (1) ...

Enterprise release

TASKS:

  • [GIT] Create branch release/M.m.p_enterprise in owncloud/android from latest (or the corresponding release tag)
  • [DOC] Update SBOM
  • [DIS] Update release notes in app and changelog in M.m.p_YYYY-MM-DD (already released version) with the proper content for the release
  • [DIS] Copy the unreleased folder in master branch into this branch, to avoid Calens conflicts problems
  • [DEV] Check and reorder release notes in ReleaseNotesViewModel.kt to assure nothing important is missing there
  • [DEV] Code review
  • [DIS] Generate final bundle and APK from last commit in the release branch
  • [QA] Design test plan
  • [QA] Test execution
  • [QA] Trigger BitRise builds for unit tests and UI tests, in case changelog conflicts avoid them in GitHub
  • [QA] QA approval
  • [DIS] Upload release APK and bundle to internal ownCloud instance
  • [GIT] Create and sign tag vM.m.p_enterprise in HEAD commit of release branch, in owncloud/android
  • [DEV] Approve and merge changes in ownBrander
  • [COM] Ping support team to block oB button
  • [COM] Ping support team to deploy oB
  • [QA] Generate final APKs from signed commit in builder machine and perform some basic checks
    • Installation of APK/bundle generated by builder machine
    • Check Feature 1 oB
    • Check Feature 2 oB
    • App update from previous version (generated in advance)
  • [COM] Notify result in internal chat
  • [COM] Ping support team to enable oB button
  • [GIT] Merge master into release/M.m.p_enterprise, fixing all the conflicts that could happen, in owncloud/android
  • [GIT] Merge without rebasing release/M.m.p_enterprise branch into master, in owncloud/android