-
Notifications
You must be signed in to change notification settings - Fork 496
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
New release #1100
Comments
#1087 Related issue. |
Saw this just this afternoon, but I wrote something in our notes this morning 😅 about this exact thing. Possibly we could establish a cadence at some point. We can talk at the next sig I guess? |
What's the usual release schedule / timeline? I would like to try out the new |
That's kinda the problem right now, we don't currently have one.
Hence this 😅 |
Any chance that a new release could be cut soon? Could really use this fix #1016 since it's making updates hard. |
I think currently there are some performance improvement efforts that involve major changes in public APIs. Maybe we should wait until they land before cutting a release? |
Which PRs? |
I think the main one is #1089. |
Any update here? Not being able to upgrade tonic because of this is a bit rough. It'd be really lovely to have a release out to fix that. |
See #1156. |
Having problems with tonic and |
There's no point in asking again and again. You can keep track of #1156 and just wait. |
#1156 has been released. |
There were no releases done since the Metrics SDK was rewritten with new specs, and also since the logging bridge was added.
Opening an issue to request a new release to be done.
The logging bridge is not quite ready for production use, but that should be okay for release as logs are opt-in only.
Releasing will make it easy to build the tracing-apppender in the tracing-opentelemetry repo, instead of temporarily doing in this repo.
The text was updated successfully, but these errors were encountered: