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

Remove semconv #5807

Merged
merged 3 commits into from
Sep 27, 2023
Merged

Remove semconv #5807

merged 3 commits into from
Sep 27, 2023

Conversation

jack-berg
Copy link
Member

Not sure if we should remove right away or give the deprecation notice a few releases to sink in. Opening the PR just to have it done and to prompt the discussion.

@jack-berg jack-berg requested a review from a team September 8, 2023 21:23
Copy link
Member

@mateuszrzeszutek mateuszrzeszutek left a comment

Choose a reason for hiding this comment

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

IMO it should be fine to remove that. There's a link to the new repo in the README, it's discoverable, I don't think there's anything more that we need to do.

@codecov
Copy link

codecov bot commented Sep 11, 2023

Codecov Report

Patch has no changes to coverable lines.

📢 Thoughts on this report? Let us know!.

Copy link
Contributor

@breedx-splk breedx-splk left a comment

Choose a reason for hiding this comment

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

😎

Comment on lines +20 to +22
If you are looking for generated classes for
the [OpenTelemetry semantic conventions][opentelemetry-semantic-conventions],
see [semantic-conventions-java][opentelemetry-semantic-conventions-java].
Copy link
Contributor

Choose a reason for hiding this comment

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

👍🏻

@jack-berg
Copy link
Member Author

Should resolve #5849 before merging.

@jack-berg
Copy link
Member Author

Anyone following please see this comment. I think we should proceed merging this without doing the maven relocation strategy.

@trask
Copy link
Member

trask commented Sep 26, 2023

Anyone following please see this comment. I think we should proceed merging this without doing the maven relocation strategy.

makes sense to me, thanks for writing up your analysis!

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.

4 participants