name: Day of launch issue
about: Use to plan Docs Content day of launch activities for major launches such as Coalesce.
title: ''[Day of launch: launch event name ([Date of launch])"
labels: day of launch
assignees: @mention
This tracking issue outlines the day of launch activities to complete before we merge the <launch event name> megabranch into main, and any wrap-up work before we unfreeze the repos. When this issue is closed, it means we've successfully published these docs 🎉
Responsible parties
[ ] @handle
Pre-launch checks
[ ] Compile a few smoke tests, which includes major pages to check after we merge the megabranch PR as well as redirects we want to check.
[ ] Freeze the repo for 3-5 days before the release.
[ ] Review all PRs being merged into the megabranch
[ ] Add anything else we need to complete before launch.
Morning of release
[ ] Update the mega branch with changes from main
[ ] Merge the megabranch :zap:
Testing and wrap up
[ ] Run smoke tests
[ ] Any other confirmation?
[ ] Unfreeze repo and announce in #team-product-docs and #shipped Slack channels
name: Day of launch issue about: Use to plan Docs Content day of launch activities for major launches such as Coalesce. title: ''[Day of launch: launch event name ([Date of launch])" labels: day of launch assignees: @mention
This tracking issue outlines the day of launch activities to complete before we merge the
<launch event name>megabranch intomain, and any wrap-up work before we unfreeze the repos. When this issue is closed, it means we've successfully published these docs 🎉Responsible parties
@handlePre-launch checks
Morning of release
Testing and wrap up