-
Notifications
You must be signed in to change notification settings - Fork 18k
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
cmd/go: revendor x/telemetry prior to go1.23.0 #67617
Comments
Note that #36905 tracks re-vendoring all dependencies in the main Go repo, which will happen soon now that we're in the freeze. This issue can be kept open after that happens if there are more x/telemetry-specific changes to bring in afterwards. |
FYI CL 589935 updated x/telemetry to v0.0.0-20240603224550-f2b69109f79b. Feel free to close this if that's enough for the needs of RC 1, or keep it open if you'd like to check in again, closer to RC 1 target date, in case more bug-fixes land in x/telemetry by then. |
Thanks. I plan to revendor again on Friday, and close this issue at that time. |
We still have a couple fixes pending, notably https://go.dev/cl/592017, which we want to land before revendoring. |
This is marked as a release blocker, is open, is not marked okay-after-RC1, and the scheduled cut for 1.23RC1 is roughly 24 hours from now. Where do we stand on this? |
I think we're good now. It looks like Michael re-vendored in https://go.dev/cl/592255. I'm going to move this to ok-after-rc1. I suspect we may have additional bug fixes after the RC. |
Change https://go.dev/cl/594021 mentions this issue: |
Change https://go.dev/cl/594019 mentions this issue: |
@findleyr I see the last cl on this was abandoned. Is this issue resolved now? |
Not resolved. The last CL was abandoned because it will instead be performed by the release team as part of the backporting process. Comment in #67617 (comment) still applies: as a matter of process, I want to ensure we have the correct telemetry code prior to the final release. |
Change https://go.dev/cl/597896 mentions this issue: |
This is a reminder issue to re-vendor x/telemetry with bug-fixes prior to go1.23rc1.
We are effectively treating x/telemetry as frozen for the moment, and want to make sure any bugfixes are included in the Go release.
The text was updated successfully, but these errors were encountered: