Prerelease v1.10.0

[MadVikingGod]

A step in #3157

Releases https://github.com/open-telemetry/opentelemetry-go/milestone/26

Added

• Support Go 1.19. (Add support for Go 1.19 #3077)
  Include compatibility testing and document support. (Add support for Go 1.19 #3077)
• Support the OTLP ExportTracePartialSuccess response; these are passed to the registered error handler. (Handle partial-success responses for OTLP trace #3106)
• Upgrade go.opentelemetry.io/proto/otlp from v0.18.0 to v0.19.0 (Bump go.opentelemetry.io/proto/otlp from v0.18.0 to v0.19.0 #3107)

Changed

• Fix misidentification of OpenTelemetry SpanKind in OpenTracing bridge (go.opentelemetry.io/otel/bridge/opentracing). (Fix opentracing.Bridge where it miss identifying the spanKind  #3096)
• The exponential histogram mapping functions have been updated with
  exact upper-inclusive boundary support following the corresponding
  specification change. (Change the inclusivity of exponential histogram bounds #2982)
• Attempting to start a span with a nil context will no longer cause a panic. (Update tracer to guard for a nil ctx #3110)
• All exporters will be shutdown even if one reports an error (Shut down all processors even on error #3091)

[codecov]

Codecov Report

Merging #3158 (48c21c2) into main (49a6536) will not change coverage.
The diff coverage is 100.0%.

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #3158   +/-   ##
=====================================
  Coverage   76.3%   76.3%           
=====================================
  Files        180     180           
  Lines      12009   12009           
=====================================
  Hits        9169    9169           
  Misses      2598    2598           
  Partials     242     242           

Impacted Files	Coverage Δ
version.go	100.0% <100.0%> (ø)
exporters/jaeger/jaeger.go	90.3% <0.0%> (-0.9%)	⬇️
sdk/trace/batch_span_processor.go	81.9% <0.0%> (+0.8%)	⬆️

[MrAlias]

The exponential histogram mapping functions have been updated with
exact upper-inclusive boundary support following the corresponding
specification change. (Change the inclusivity of exponential histogram bounds #2982)

This is not included in this release and needs to be removed from the changelog entry.

[jmacd]

This is not included in this release and needs to be removed from the changelog entry.

What happened to this change? I've been waiting to refer to it from opentelemetry-collector, here: open-telemetry/opentelemetry-collector#5938

[jmacd]

I'd like to suggest we include the exponential histogram mapping function change in this release,
#3159

[MadVikingGod]

@MrAlias Did I miss something? Maybe this needs to be a v1.10, and metrics/v0.32. release?

[MrAlias]

@MrAlias Did I miss something? Maybe this needs to be a v1.10, and metrics/v0.32. release?

We had agreed the next metric release is going to be for the alpha SDK. I think the versioning is correct as is.

This is not included in this release and needs to be removed from the changelog entry.

What happened to this change? I've been waiting to refer to it from opentelemetry-collector, here: open-telemetry/opentelemetry-collector#5938

I thought it was agreed the commit hash version of main would be used as a dependency for this package?

[jmacd]

I thought it was agreed the commit hash version of main would be used as a dependency for this package?

I can do that. I've done that in otel-launcher-go but I don't feel comfortable doing that for the OTel collector. I proposed #3159 because it seems to avoid leaving clutter in the sdk/metric/aggregator package where the new SDK doesn't want it to belong, it's fine to let this go to another release.

[jmacd]

I'd prefer if #3156 could be included in this release, approved either way.

[jmacd]

@MadVikingGod sorry to create trouble. I think it's OK not to create a v0.32 metrics release, especially if we can prioritize moving the sdk/metric/aggregator/exponential support into a new location to be included in the next 1.x release.

[MadVikingGod]

I don't remember the v0.32 discussion, but I'm fine with that.

I have reverted the changes for those versions (v0.32.0), and have removed the changelog entry.

[MadVikingGod]

As #3156 is also a customer impacting bugfix I also would like to see that in this release. I will delay until that is landed in main, and can be added to this PR.