status-im
/
status-react
mirror of https://github.com/status-im/status-react.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
status-react/.github/ISSUE_TEMPLATE/release-issue.md

3.6 KiB
Raw Blame History

name about title labels assignees
Release umbrella issue Release Issue Mobile release release

Issue to manage mobile release

Scope

https://github.com/status-im/status-react/milestone/

  • release notes:
  • release branch:

Testing info

Main test suite: Upgrade (e2e):

Builds in TestFlight and PlayStore to push as a release

Process

1) Kick-off

  • 1. Translation PRs is merged before cutting branch (Jinho)
  • 2. Prepare scope of visible changes based on commits history, started from previous release branch cut (example)
  • 3. Update RELEASES.md with release notes (make PR based on previous step)
  • 4. Create 1.14.0 release branch and get successful builds (doc is here so, testing can be started)
  • 5. Based on release scope, ask for comms (Jonny)
  • 6. Make sure that assets (screenshots, video) in stores are up to date. If should be updated, ask @cammellos for help

2) Testing

  • Dogfooding (add notes, if it was held)
  • Regression testing for release candidate build
  • Upgrade tests
  • Fix known blocker(s) found during regression testing
Blockers
  • 1 blocker:

=============================================================================================

  • Cherry-pick fix(es) to the release branch
  • Verify fix(es) on new release candidate build
  • Retest
  • Keep release build forever (button in Jenkins)

3) Submission

  • 1. Release notes written and added (500 character limit for updates (Android) and PR for RELEASES.md is ready to be merged (from 1.3 step)
  • 2. Submit beta version for Android (Open Testing in Play Store)
  • 3. Submit iOS build to Apple review (instruction, be careful - low quality of audio)
  • 4. Play store content reviewed and updated
  • 5. Privacy policy reviewed and updated (ask in channel)
  • 6. Countries to be excluded (ask in channel)
  • 7. Changes to our FAQ made (should be checked and if any changes needed, ask Jakub to made them)
  • 8. Prepare PR for F-droid build (instruction)

4) Before publishing

  • 1. Translations for comms available (marketing, ask in the channel)
  • 2. Promotional content ready (marketing, ask in channel)
  • 3. Upload builds for DO store, https://dev.status.im/ (Jakub)

5) At time of publishing