Skip to content

Latest commit

 

History

History
124 lines (99 loc) · 5.77 KB

release_template.md

File metadata and controls

124 lines (99 loc) · 5.77 KB
Raw
name about title labels assignees
Release
List of checklist to accomplish for the ownCloud team to finish the release process
[RELEASE]
Release

Open Release

TASKS:

  • [DOC] Ping in #android-dev-internal about the new release (@mmattel)
  • [GIT] Create branch release/M.m.p in owncloud/android from master
  • [DEV] Update version number and name in build.gradle in owncloudApp module
  • [DEV] Update SBOM
  • [DIS] Create a folder for the new version like M.m.p_YYYY-MM-DD inside the changelog folder
  • [DIS] Move all changelog files from the unreleased folder to the new version folder
  • [DEV] Check release notes in ReleaseNotesViewModel.kt to assure nothing important is missing there
  • [DIS] Prepare post in central.owncloud.org (Category:News + Tag:android)
  • [DIS] Check for new screenshots in Play Store / GitHub repo and generate them
  • [DIS] Generate final bundle from last commit in owncloud/android
  • [QA] Design Test plan
  • [DEV] Code Review
  • [QA] Regression Test execution
  • [QA] QA Approval
  • [DIS] Upload release APK and bundle to internal owncloud instance
  • [DOC] Ping in #android-dev-internal that we are close to sign the new tags (@mmattel)
  • [DIS] Upload & publish release bundle and changelog in Play Store
  • [DIS] Update screenshots and check they are OK in Play Store and in README.md (if needed)
  • [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
  • [GIT] Publish a new release in owncloud/android
  • [DIS] Release published in Play Store
  • [DIS] Publish post in central.owncloud.org (Category:News + Tag:android)
  • [COM] Inform #general in public chat that release is out
  • [GIT] Merge without rebasing release/M.m.p branch into master, in owncloud/android
  • [DOC] Ping @TheOneRing 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
  • [DEV] Update SBOM
  • [DIS] Create a folder for the new version like M.m.p_YYYY-MM-DD inside the changelog folder with the proper fixes
  • [DIS] Copy the unreleased folder in master branch to changelog folder in this branch, to avoid Calens' conflicts problems
  • [DEV] Add release notes to ReleaseNotesViewModel.kt (in case patch release before OEM)
  • [DIS] Check for new screenshots in Play Store / GitHub repo and generate them
  • [DIS] Generate final bundle from last commit in owncloud/android
  • [DEV] Code Review
  • [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 & publish release bundle and changelog in Play Store
  • [DIS] Update screenshots and check they are OK in Play Store and in README.md (if needed)
  • [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
  • [GIT] Publish a new release in owncloud/android
  • [DIS] Release published in Play Store
  • [COM] Inform #general in public chat that release is out
  • [GIT] Merge master into release/M.m.p, fixing all the conflicts that could happen
  • [GIT] Merge without rebasing release/M.m.p branch into master, in owncloud/android
  • [DOC] Ping @TheOneRing to update release information in https://owncloud.com/mobile-apps/

QA

QA checks:

  • Smoke test
  • Upgrade test

Bugs & improvements:

  • (1) ...

OEM Release

TASKS:

  • [GIT] Create a new branch release/M.m.p_oem (optional)
  • [DIS] Update release notes in app with the proper content for oem release
  • [GIT] Create and sign tag vM.m.p_oem in HEAD commit of release/M.m.p_oem branch
  • [DEV] Approve and merge changes in ownBrander
  • [OPS] Block oB button
  • [OPS] Deploy oB
  • [QA] Generate final APKs files from signed commit in builder machine and perform some basic checks:
    • Installation of apk/aab generated by builder machine
    • Check Feature 1 oB
    • Check Feature 2 oB
    • App update from previous version (generated in advance)
  • [QA] Notify result in #ownbrander
  • [OPS] Enable button
  • [GIT] Fix conflicts in branch if they happen. GitHub option will help and will merge master into release branch, getting it ready to fast forward
  • [GIT] Merge without rebasing release/M.m.p_oem branch into master, in owncloud/android