Release checklist for v1.0 (scheduled)

[jhnstn]

This checklist is for the scheduled release v1.0.

Release Tasks

Pre release

• [ ] Review Release process notes
• [ ] Notifiy open Gutenberg Mobile PRs assigned to {{VERSION_NUMBER}} milestone.
  Message Template

Hello!
We will cut the {{VERSION_NUMBER}} release on {{RELEASE_DATE}}.
I plan to circle back and bump this PR to the next milestone then,
but please let me know if you’d rather us work to include this PR in {{VERSION_NUMBER}}.
Thanks!

• [ ] Create WPiOS and WPAndroid builds from develop and complete the general writing flow tests.
• [ ] Clone or update the release toolkit and review the release script instructions.

Create the Release {{RELEASE_DATE}}

• [ ] Verify Aztec is up to date.
• [ ] Run ./release_automation.shfrom the release toolkit to generate the main apps integration PRs *.
• [ ] Notify team that the release has been cut. (message template)
• [ ] Verify localization string files have been generated properly.
• [ ] Update Unreleased section in RELEASE-NOTES.txt and gutenberg/../CHANGELOG.md
• [ ] Perform quick smoke test of the editor on both iOS and Android builds.
• [ ] Update Gutenberg Mobile PR description. Make sure the "Changes" section informs testers on what is in the release.
• [ ] Mark all 4 PRs ready for review.

Aztec Release

• [ ] Verify all Aztec PRs attached to the "Next Release" milestone or PRs with changes required for the this Gutenberg release have been merged.
• [ ] Open a PR on Aztec repo to update the CHANGELOG.md and README.md files with the new version name.
• [ ] Create a new release and name it with the tag name from step 1.
• [ ] Follow these instructions to update Aztec-iOS and Aztec-Android.
• [ ] Update the Aztec version references in gutenberg-mobile and gutenberg

Integrate the Release {{RELEASE_DATE}}

• [ ] Verify gutenberg ref within the gutenberg-mobile release branch is pointing to the latest commit in Gutenberg release branch.
• [ ] Create and push a rnmobile/{{VERSION_NUMBER}} git tag for the head of Gutenberg release branch.
• [ ] Update bundles in the Gutenberg Mobile release branch.
• [ ] Merge gutenberg-mobile PR to trunk using the "Create a merge commit" option. WARNING do not merge gutenberg PR to trunk yet.
• [ ] Create a new Gutenberg moble release.
• [ ] Update Gutenberg mobile references in the main apps.
• [ ] Re-run optional tests on main apps PRs.
• [ ] Merge main apps PSs to the respective develop branches.
• [ ] Notify team that the release is now in the main apps develop branches
  Message Template

Sync Release

• [ ] Merge Guteberg release PR to gutenberg/trunk.
• [ ] Merge release changes back to gutenberg-mobile/develop e.g. trunk -> merge_release_{{VERSION_NUMBER}}_to_develop -> develop