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.

Sign up for GitHub

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

Jump to bottom

Shall we release 1.0? #69

Closed
josevalim opened this issue Dec 3, 2020 · 5 comments · Fixed by #71
Closed

Shall we release 1.0? #69

josevalim opened this issue Dec 3, 2020 · 5 comments · Fixed by #71

Comments

@josevalim
Copy link
Contributor

No description provided.

@GregMefford
Copy link

GregMefford commented Dec 3, 2020 •
edited
Loading

Sure! 😁 :shipit: 🎉 🚀

@josevalim
Copy link
Contributor Author

Fantastic. Btw, when updating dependencies that depend on telemetry, let's update them to: "~> 0.4 or ~> 1.0", so we don't force everyone to migrate to 1.0 immediately (or worse, have conflicting deps).

@whatyouhide
Copy link
Contributor

👍 on this, it's great!

@tsloughter
Copy link
Contributor

+1 with the caveat that we wait for erlang/rebar3#2370 :)

@binaryseed
Copy link
Contributor

Awesome!

I'd love to come to a decision on #48 but that shouldn't block a 1.0

@arkgil arkgil mentioned this issue Mar 5, 2021
Merged
@arkgil arkgil closed this as completed in #71 Jul 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Release 1.0.0 beam-telemetry/telemetry
5 participants
@josevalim @tsloughter @binaryseed @GregMefford @whatyouhide