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

Release v0.10.1 #212

Closed
lizthegrey opened this issue Aug 13, 2020 · 3 comments · Fixed by #216
Closed

Release v0.10.1 #212

lizthegrey opened this issue Aug 13, 2020 · 3 comments · Fixed by #216
Assignees
Labels
question Further information is requested
Milestone

Comments

@lizthegrey
Copy link
Member

It'd be helpful to let -go-contrib evolve a little faster than -go, so that for instance people can migrate in advance to the moved othttp instrumentation instead of having things be temporarily broken between v0.11 of -go and -go-contrib being released. Thoughts?

@MrAlias
Copy link
Contributor

MrAlias commented Aug 13, 2020

Seems reasonable to me 👍

@MrAlias MrAlias added the question Further information is requested label Aug 13, 2020
@MrAlias MrAlias self-assigned this Aug 13, 2020
@lizthegrey
Copy link
Member Author

Not actually blocking for me, it turns out https://pkg.go.dev/mod/go.opentelemetry.io/contrib/instrumentation/net/http@v0.0.0-20200813041938-b948cd370862 will work fine, but ideally still it'd be tagged with v0.10.1

@MrAlias
Copy link
Contributor

MrAlias commented Aug 13, 2020

Looking to merge PRs that are ready and then get this out.

plantfansam referenced this issue in plantfansam/opentelemetry-go-contrib Mar 18, 2022
also include byte allocation report.
 rename file to match http_trace_context propagator.
@pellared pellared added this to the untracked milestone Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants