-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release: v19.2.3 #44455
Comments
Outdated, see signoff list below.
|
Restarting Release. New candidate sha: 2353f82 |
Roachtest failures: https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_NightlySuite/1719820 SignoffsKV
appdev cdc
sql-schema
|
@nvanbenschoten is going to look further into the cdc rangefeed crasher. For context the issue is a node died. Here's the panic:
|
I was remembering correctly. We also saw this in #43056 (comment):
The bug that #42939 fixed was present in 19.2 and we haven't backported that change, so I think it's likely that we're seeing that issue. So we have two options here:
I think that change is small and safe enough to backport, but I'd like to get @tbg to sign off on that as well. Was there a reason we didn't backport it before? The backport was mentioned in #42939 (review). |
I've checked off all the "KV" ones because I didn't see anything interesting in any of the failures. |
schemachange/mixed/tpcc sign off here -- https://cockroachlabs.slack.com/archives/CARM0PTK4/p1580919731008700 |
Candidate 2353f82
Nightly Suite:
https://teamcity.cockroachdb.com/viewLog.html?buildId=1719820&buildTypeId=Cockroach_Nightlies_NightlySuite
Deployment Dashboards
Release process checklist
Prep date:
WIP fill in date to roll out: usually Monday, a week before the release WIP
Candidate SHA
above, notify #release-announce of SHA.Deployment status
above with clusters andNightly Suite
with the link to Nightly TeamCity JobOne day after prep date:
Get signoff on roachtest failures
Keep an eye on clusters until release date. Do not proceed below until the release date.
Release date: Feb 4 or 5th (moving 1 day forward)
Check cluster status
Tag release (Release Tag)
Bless provisional binaries (Build)
For production or stable releases in the latest major release series
Update docs
External communications for release
Clean up provisional tag from repository
The text was updated successfully, but these errors were encountered: