Things to remember/check

[erkannt]

• production deployment has production config and secrets
• chart version pinned for prod deployment
• keep using master-hash-date images or switch to semver?
• is team happy with the release gating in place? Go over canary config, repo pipelines.
• merge chart-integration branch on reviewer-reporter
• tidy up aws Database Migration Service tasks, endpoints and instances
• reset reviewer-staging RDS
• shrink xpub prod and staging RDS back to 5GB (or fully remove them?)
• remove xpub deployments (builder)
• archive/delete no longer needed libero repos

[Cooryd]

manuscript rows
90f66de1-4732-44e3-89a8-5c356374d629
and
8ae61c5d-c76c-4bdb-a0f8-3f08356c9181 had un-migratable data in theirpreviously_submitted columns so this will need to be manually re-added after launch.

https://elifesciences.slack.com/archives/C6LKMFK5Z/p1600942181003500
https://elifesciences.slack.com/archives/C6LKMFK5Z/p1600944140007500

[Cooryd]

Re-instated the previously_submitted data for manuscript row 90f66de1-4732-44e3-89a8-5c356374d629 and 8ae61c5d-c76c-4bdb-a0f8-3f08356c9181

[hdrury1]

These are now mostly cleanup tasks that don't have their own tickets (yet). The top two unchecked todos are discussions/questions regarding how we gate deployments. Originally we had planned to use semver and we still have some build pipelines set up for this but never use them. So either we modify our gating/image tagging/updating procedures or remove the unused pipelines and docker-compose files.