Skip to content
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

Closed
cijothomas opened this issue Jun 8, 2023 · 13 comments
Closed

New release #1100

cijothomas opened this issue Jun 8, 2023 · 13 comments

Comments

@cijothomas
Copy link
Member

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.

@cijothomas
Copy link
Member Author

#1087 Related issue.

@hdost
Copy link
Contributor

hdost commented Jun 14, 2023

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?

@chesedo
Copy link

chesedo commented Jun 15, 2023

What's the usual release schedule / timeline?

I would like to try out the new logs feature on otlp, But maybe I can tell cargo to pull from git main if I can only figure out how to align the versions with tracing 😅

@hdost
Copy link
Contributor

hdost commented Jun 15, 2023

What's the usual release schedule / timeline?

That's kinda the problem right now, we don't currently have one.

Saw this just this afternoon, but I wrote something in our notes this morning sweat_smile about this exact thing. Possibly we could establish a cadence at some point. We can talk at the next sig I guess?

Hence this 😅

@purkhusid
Copy link

Any chance that a new release could be cut soon? Could really use this fix #1016 since it's making updates hard.

@TommyCpp
Copy link
Contributor

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?

@hdost
Copy link
Contributor

hdost commented Jun 30, 2023

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?

@djc
Copy link
Contributor

djc commented Jul 1, 2023

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.

@Sushisource
Copy link

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.

@djc
Copy link
Contributor

djc commented Jul 25, 2023

See #1156.

@HectorMRC
Copy link

Having problems with tonic and with_metadata as well. Any ETA for a v0.20.0 release?

@djc
Copy link
Contributor

djc commented Jul 30, 2023

There's no point in asking again and again. You can keep track of #1156 and just wait.

@jtescher
Copy link
Member

#1156 has been released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants