Iván Valdés Castillo

We may want to hold the release after 7/2, as according to SIG-release's email > There is a Go update being released on 07/02 I do see some outstanding changes...

Would you guys be available Monday, July 8th, at 11 a.m. PT? I'll be out next week starting Tuesday, so I won't be available if you want to schedule it...

@jmhbnz, after updating Go to address vulnerabilities (#18269), I think we now can release 3.4.34, right?

> What is the CVE score? NIST don't list it yet https://nvd.nist.gov/vuln/detail/CVE-2024-24791. Our patch release criteria is 7.5 That's a good point. I think there's no rush, and ultimately, there...

> Will do some review soon, we also need to take a close look at recent bug reports and see if anything needs to be included: https://github.com/etcd-io/etcd/issues?q=is%3Aissue+label%3Atype%2Fbug+created%3A%3E%3D2024-04-30 I reviewed these...

We have scheduled this release for today, Friday, July 19th, at 1 pm PT.

> Please also update the release date, thx Done in #18355.

> > > 2. gcr.io/etcd-development & quay.io/etcd are now deprecated > > > > > > The registries have already been used for about a decade. We should keep it...

@ahrtr, got it. We're all aligned. It's a matter of updating documentation and tagging everyone involved.

This issue became apparent when @upodroid started building from the CI (refer to the [stage GCS bucket](https://console.cloud.google.com/storage/browser/k8s-staging-etcd/releases?pageState=(%22StorageObjectListTable%22:(%22f%22:%22%255B%255D%22))&project=k8s-staging-etcd), please note the `v3.6.0-alpha.0-6346-g813f28bcb` prefix). Although it was present in the main branch...