release: v19.2.11

[celiala]

Version Bincheck: cockroachdb/bincheck#226

---

Tentative Release Date: Mon, 12 Oct, 2020
Candidate SHA: e450c34dbf33745d889f41e1b1ea65197c1506fc (e450c34)
Deployment status: WIP EDIT ME WIP.
Tag: v19.2.10-39-ge450c34
Make and Publish Build: #361
Qualify Build: #178
Publish Cockroach Release: WIP EDIT ME WIP.

CC Clusters Running the Build:

• db-dev-1, in Peter's Org org. SREOPS-295

Admin UI for Qualification Clusters:

Created	v19.2.10	v19.2.11	2 days	4 days
10/6, 7pm	v19.2.10	v19.2.11	10/8 5p	10/12 11a
Overview (+QPS, Latency)	Overview	Overview	✅	✅
SQL	SQL	SQL	✅	✅
Replication	Replication	Replication	✅	✅

Working Tags:

• Release Staging Tag: WIP EDIT ME WIP.
• staging-* tag: WIP EDIT ME WIP.

Release process checklist

Prep date: WIP fill in date to roll out: usually Monday, a week before the release WIP

• Pick a SHA
  • fill in Candidate SHA above
  • fill in staging-* Tag above
  • fill in Release Staging Tag above
  • fill in Make and Publish Build above
  • fill in Qualify Build above
  • email thread on releases@

Release Qualification

• Ask SRE to run the build on some CC clusters
• Verify node crash reports
• Deploy to test clusters
• fill in all WIP elements above (Admin UI, etc.)

One day after prep date:

• Keep an eye on clusters until release date.

Do not proceed below until the release date.

Release date: WIP fill in date: usually Monday WIP

• Check cluster status

  • Destroy clusters

• Publish Cockroach Release

• Acked security@ and release-engineering-team@ on the generated AWS S3 bucket write alert to confirm these writes were part of a planned release (See Publish Cockroach Release for details).

• Check binaries

• Check docker image

• If applicable, update the map that roachtests use to map a version to a previous version, to reference the newly tagged version

• Remove staging branch / tags from repository

• For production or stable releases in the latest major release series (in August 2020, this is the v20.1 series)

  • Update the Homebrew Formula
  • Update the image tag in our Orchestrator configurations

• For production or stable releases

  • Announce version to the registration cluster

• Update docs

• External communications for release

Cleanup:

• Remove staging branch / tags from repository
• Destroy roachprod clusters

[blathers-crl]

Hi @celiala, please add a C-ategory label to your issue. Check out the label system docs.

While you're here, please consider adding an A- label to help keep our repository tidy.

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.}

[celiala]

Release is complete