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

Prepare 0.24.0 release #142

Merged
merged 4 commits into from
May 29, 2024
Merged

Prepare 0.24.0 release #142

merged 4 commits into from
May 29, 2024

Conversation

djc
Copy link
Collaborator

@djc djc commented May 24, 2024

No description provided.

@djc djc requested a review from jtescher as a code owner May 24, 2024 07:26
Copy link
Contributor

@Xuanwo Xuanwo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work!

@Xuanwo
Copy link
Contributor

Xuanwo commented May 24, 2024

By the way, I'm also happy to lend a hand if you need extra help.

@djc
Copy link
Collaborator Author

djc commented May 24, 2024

@Xuanwo if you want to help out reviewing #129 (formerly #117) and/or #124 that would be great!

CHANGELOG.md Show resolved Hide resolved
@kudlatyamroth
Copy link

when this will be released ?

@djc
Copy link
Collaborator Author

djc commented May 27, 2024

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.

@djc djc force-pushed the prepare-0.24.0 branch from 13b5dcc to 5b4cfbf Compare May 27, 2024 11:51
@@ -1,10 +1,6 @@
[package]
name = "tracing-opentelemetry"
version = "0.23.0"
authors = [
"Julian Tescher <julian@tescher.me>",
Copy link
Member

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>"
Copy link
Member

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.

Copy link
Collaborator Author

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?

Copy link
Member

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)
Copy link
Member

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).

@djc djc mentioned this pull request May 29, 2024
djc added 2 commits May 29, 2024 10:52
This doesn't seem to be useful for a small single crate repository.
@djc djc force-pushed the prepare-0.24.0 branch from 5b4cfbf to eab0ffb Compare May 29, 2024 08:52
@djc
Copy link
Collaborator Author

djc commented May 29, 2024

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.

@djc djc merged commit de42149 into v0.1.x May 29, 2024
15 checks passed
@djc
Copy link
Collaborator Author

djc commented May 29, 2024

  • Published tracing-opentelemetry v0.24.0 at registry crates-io
  • [new tag] v0.24.0 -> v0.24.0

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

Successfully merging this pull request may close these issues.

5 participants