This ticket is to control for all the requirements for the upcoming release before the Pull Request is opened. This should hold any tasks or bug fixes unique to the release branch. It should also collect any text for What's New and any content changes for the app stores.
This ticket should be complete by Monday Nov 18, 2024
Release Checklist
[ ] What's new content (App Store) - required
[ ] What's new content (In app/Alert Box) - optional
[ ] Content updates
Sign-offs:
- [ ] QA **Due Thursday Nov 14, 2024**
- [ ] Product **Due Sunday Nov 17, 2024**
- [ ] Mobile Release Manager **Due after 10am EST Monday Nov 18, 2024**
## Release version
If there aren't any new features, use standard messaging: We added general improvements and fixed a few bugs.
If a Flagship team decides to update the App Stores What's New content, their work should be done in a ticket and provided to the release manager, who will then update this section. If not provided, it's assumed not to be used.
What's New content (In App/Alert Box) - optional
This work is to be completed by Flagship teams before RC branch is cut and completed by engineering. Flagship team to provide release manager with the ticket this work was completed in for reference.
App Store content changes?
All changes should be made to the files in the repo and not directly to the stores.
Indicate NA if no changes.
Release for Monday Nov 25, 2024
This ticket is to control for all the requirements for the upcoming release before the Pull Request is opened. This should hold any tasks or bug fixes unique to the release branch. It should also collect any text for What's New and any content changes for the app stores.
This ticket should be complete by Monday Nov 18, 2024
Release Checklist
Sign-offs:
- [ ] QA **Due Thursday Nov 14, 2024** - [ ] Product **Due Sunday Nov 17, 2024** - [ ] Mobile Release Manager **Due after 10am EST Monday Nov 18, 2024** ## Release versionchanel-6808-create-system-for-updating-names-on-release-tickets
What's New content (App Store) - required
If there aren't any new features, use standard messaging: We added general improvements and fixed a few bugs.
If a Flagship team decides to update the App Stores What's New content, their work should be done in a ticket and provided to the release manager, who will then update this section. If not provided, it's assumed not to be used.
What's New content (In App/Alert Box) - optional
This work is to be completed by Flagship teams before RC branch is cut and completed by engineering. Flagship team to provide release manager with the ticket this work was completed in for reference.
App Store content changes?
All changes should be made to the files in the repo and not directly to the stores. Indicate NA if no changes.
Severe bugs:
Regression Testing
QA Testrail Regression Test Run Here