05d0e15359
A Github issue template to help formalizing the release process, in order to avoid human errors in the process. Closes: https://github.com/damus-io/damus/issues/2752 Signed-off-by: Daniel D’Aquino <daniel@daquino.me>
1.9 KiB
1.9 KiB
name, about, title, labels, assignees
| name | about | title | labels | assignees |
|---|---|---|---|---|
| App release process | Begin preparing for a new app release | Release: | release-tasks |
A new version release. Please attempt to follow the release process steps below in the order they are shown.
TestFlight release candidates
Release candidate 1
Version: [Enter full build information for the release candidate, including major and minor version number, build number, and commit hash]
- Merge in all needed changes to
master - Check CI, make sure it is passing
- Prepare preliminary changelog as a draft PR: [Enter PR link to changelog here]
- Make a release build and submit to the internal TestFlight group via our new Release candidate workflow in Xcode Cloud.
- Prepare short screencast style video with main changes for the announcement
- Publish release build to these TestFlight groups:
- Alpha testers group
- Translators group
- Purple group
- Publish announcement on Nostr
[Duplicate this release candidate section if there is more than one release candidate]
App Store release
- Release candidate checks:
- Release candidate has been on Purple TestFlight for at least one week
- No blocker issues came from feedback from Purple users (double-check)
- Check with stakeholders
- Check with developers & product for any release showstoppers (e.g., critical newfound bugs)
- Thorough check on release notes
- Submit to App Store review (with manual publishing setting enabled)
- Get App Store approval from Apple
- Prepare announcement
- Publish on the App Store and make announcement
- Publish changelog and tag commit hash corresponding to the release
- Perform a version bump on the repository, in preparation for the next release
Notes/others
Enter any relevant notes here