-
Notifications
You must be signed in to change notification settings - Fork 86
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
Prepare 0.24.0 release #142
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work!
By the way, I'm also happy to lend a hand if you need extra help. |
when this will be released ? |
I'm hoping to get some feedback from @jtescher (or maybe @davidbarsky?). If I don't get any in, say, 48 hours, I'll merge and publish. |
@@ -1,10 +1,6 @@ | |||
[package] | |||
name = "tracing-opentelemetry" | |||
version = "0.23.0" | |||
authors = [ | |||
"Julian Tescher <julian@tescher.me>", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is up to julian; i'd check with him first.
version = "0.23.0" | ||
authors = [ | ||
"Julian Tescher <julian@tescher.me>", | ||
"Tokio Contributors <team@tokio.rs>" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'd consider keeping this one or getting an otel-specific alias here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given the existence of RFC 3052 and the concerns it enumerates, why?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i don't have strong feeling; i just think credit is important!
|
||
### Fixed | ||
|
||
- Set span end time when it exists (#124) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i won't block this, but i've mentioned my concerns here: #124 (comment).
This doesn't seem to be useful for a small single crate repository.
I'm going forward with this release to unlock the use of opentelemetry 0.23 for the community. @davidbarsky thanks for your feedback -- I've considered it but given the discussion so far I'm still feeling good about the span end time change in #124 and the authors metadata change I made in this PR. @jtescher (or anyone else), happy to have more discussion about the span end time change in #124 and the authors metadata change I made in this PR -- we can revert both changes in a semver-compatible API which I'd be happy to work on if we decide it's needed. |
|
No description provided.