v0.0.10 release plan

[cwe1ss]

Now that #55 and #59 are merged, we should do a release soon.

My main open question is whether we should wait for the upcoming v0.12.0 release of OpenTracing? I'd like to release that one by the end of next week.

Anything else that should be included?

[Falco20019]

Let's wait for #61 and opentracing/opentracing-csharp#92. Should be fine if it's just one more week.

[ScottGuymer]

👋 Hi!
Im dipping my toes into Jaeger tracing for my dotnet core apps.

Any ideas when this is going to be released?

I realise there is some refactoring to do once it is. Im having trouble getting the trace to speak to a remote agent at the moment and wondered if this new version might solve the issues..

Although im not sure what the specific issue is yet!

[Falco20019]

Should be released tomorrow :) OpenTracing v0.12.0 for which we waited is released now. So just some reviews left.

Configuration will be easier with the new version. I also plan to get the tutorial for C# merged tomorrow.

[ScottGuymer]

Ok thats good news. Ill configure against a local build for now.

Im also happy to contribute back anything I can too.

[Falco20019]

@cwe1ss I think we now have everything ready for v0.0.10 👍 Can you push the artifacts to NuGet?

[cwe1ss]

I couldn't do the release because the NuGet credentials in the appveyor.yml seem to be wrong (build output). I will create a separate issue with instructions for Yuri.

[Falco20019]

Very strange, since we changed it here the last time. Thanks for informing @yurishkuro

[cwe1ss]

The release succeeded this time! 🍻

As we're no longer using the Jaeger.Core and Jaeger.Transport.Thrift packages, I'd like to unlist all previous Jaeger versions on NuGet.org to reduce confusion. Any objections?

[Falco20019]

Yes, I think unlisting them should be the cleanest option.

[cwe1ss]

I unlisted these packages.