Delivery tracking issue 9.28-10.12

[beyang]

To prioritize

• Update Upgrade instructions @abeatrix
• Automated AMI generation (e.g., via packer) @abeatrixAMIs for all AWS regions #42256
  AMIs for all AWS regions
• One-click AWS CloudFormation launch template @jac
• Move Sourcegraph AMIs under separate AWS account @slimsag
• Foundational Technical Review for AWS Marketplace (chat) @beyang

Questions

• What's our current process for updating the Docker Compose docs? - A: there's automation around this.

Punt

• One-click Azure launch Adding AMI support for Azure #42661
• One-click GCP launch Adding AMI support for GCP #42660
• Migration path from (and deprecation of) Docker Compose to k3s
• One-click config export (chat, https://github.com/sourcegraph/sourcegraph/discussions/37930, https://github.com/sourcegraph/sourcegraph/issues/39588)
• Health Status Checker (chat, doc)

Plan

Tracked issues

Legend

• 👩 Customer issue
• 🐛 Bug
• 🧶 Technical debt
• 🎩 Quality of life
• 🛠️ Roadmap
• 🕵️ Spike
• 🔒 Security issue
• 🙆 Stretch goal

[felixfbecker]

@abeatrix did you mean to close the entire tracking issue with https://github.com/sourcegraph/sourcegraph/pull/42453, or only tick off the first item?

[abeatrix]

@abeatrix did you mean to close the entire tracking issue with https://github.com/sourcegraph/sourcegraph/pull/42453, or only tick off the first item?

Woops I only meant to close the first item, I think it was closed automatically when one of my PR was closed, thanks for catching this 😓

[beyang]

Closing in favor of: https://github.com/orgs/sourcegraph/projects/290/views/1