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

Stability Roadmap? #1080

Closed
thequailman opened this issue Aug 23, 2020 · 3 comments · Fixed by #1106
Closed

Stability Roadmap? #1080

thequailman opened this issue Aug 23, 2020 · 3 comments · Fixed by #1106

Comments

@thequailman
Copy link

Hello, I am considering using this library but looking at the current master docs vs the latest release (0.10.0), there seems to be a lot of changes pending--labels for instance seems new and the examples are quite different. What does the roadmap towards 1.0 look like for this library? When will the API stabilize?

@Aneurysm9
Copy link
Member

There is indeed a great deal in flux right now. We have just completed a restructuring of the Go modules in this repository to minimize the footprint of including the API in an instrumented library and the OTel Spec itself is undergoing rapid change as we try to nail down any final BC-breaking changes for the upcoming trace specification RC. You can track progress toward that stabilization milestone here. As the specification stabilizes we are attempting to keep up with it in this project, but we will obviously lag somewhat behind. The issues remaining in this repository that must be completed before a GA release can be tracked with the release:required-for-ga label.

@MrAlias
Copy link
Contributor

MrAlias commented Aug 27, 2020

I've added a section to the main README that links to our new project boards and milestones. Hopefully this helps make this journey to stability a bit more visible.

@thequailman
Copy link
Author

@MrAlias thank you that helps out a lot!

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 a pull request may close this issue.

3 participants