-
Notifications
You must be signed in to change notification settings - Fork 73
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
v0.12.0 Release Plan #92
Comments
Hey @cwe1ss - thanks for collating the release milestone. I think what you have proposed all makes sense and I agree including the additional three commits would be beneficial. Regarding your open questions:
|
Alright, to move things forward, I went ahead and merged some PRs and put a time limit on the others. I'd like to do a release next week if that's ok for everyone. |
I merged the other PRs and created the "0.12.0-rc1" release candidate! Release notes: https://github.com/opentracing/opentracing-csharp/releases/tag/0.12.0-rc1 Please give it a try! I'd like to do the final release at the end of next week if there's no objections. PS: Not sure yet if we should include #84 as well?! There's no definitive answer yet in that linked issue. |
Thanks for all your work on this @cwe1ss |
No objections so far, so I'll go ahead and release it NOW. |
v0.12.0 has been released! Release notes: https://github.com/opentracing/opentracing-csharp/releases/tag/0.12.0 |
Milestone details: https://github.com/opentracing/opentracing-csharp/milestone/5
Relevant merged changes so far:
These have been small non-breaking changes. We could do a servicing release with them but I'd prefer having fewer big releases to make sure people don't have to update their dependencies too often. For that reason, I'd like to also get some other important issues done.
My candidates would be:
Would be great to get some more feedback/approval on these issues to get them done asap.
Other open questions:
What's your opinions on the frequency of releases? Anything else that should be included?
The text was updated successfully, but these errors were encountered: