Merge the new_sdk/main branch into main
Blocked by all issues in https://github.com/open-telemetry/opentelemetry-go/milestone/22. This will be the last issue that closes the milestone.
This needs to include deleting the new_sdk/example branch. It will no longer be needed.
The PR number needs to be added to the changelog entries added in #3150
Merging will orphan the following packages:
go.opentelemetry.io/otel/sdk/metric/aggregator/aggregatortestgo.opentelemetry.io/otel/sdk/metric/aggregator/histogramgo.opentelemetry.io/otel/sdk/metric/aggregator/lastvaluego.opentelemetry.io/otel/sdk/metric/aggregator/sumgo.opentelemetry.io/otel/sdk/metric/aggregatorgo.opentelemetry.io/otel/sdk/metric/controller/basicgo.opentelemetry.io/otel/sdk/metric/controller/controllertestgo.opentelemetry.io/otel/sdk/metric/controller/timego.opentelemetry.io/otel/sdk/metric/export/aggregationgo.opentelemetry.io/otel/sdk/metric/exportgo.opentelemetry.io/otel/sdk/metric/numbergo.opentelemetry.io/otel/sdk/metric/processor/basicgo.opentelemetry.io/otel/sdk/metric/processor/processortestgo.opentelemetry.io/otel/sdk/metric/processor/reducergo.opentelemetry.io/otel/sdk/metric/registrygo.opentelemetry.io/otel/sdk/metric/sdkapigo.opentelemetry.io/otel/sdk/metric/selector/simple
Do we want to plan a deprecation strategy for these? (Related to https://github.com/open-telemetry/opentelemetry-go/issues/2328)
Question about go.opentelemetry.io/otel/sdk/metric/aggregator/exponential/mapping (which exists today and should stay somewhere). I think it's OK if that package moves.
Question about go.opentelemetry.io/otel/sdk/metric/aggregator/exponential/mapping (which exists today and should stay somewhere). I think it's OK if that package moves.
Indeed, this needs to be migrated to the new SDK. Please create an issue and add it to the beta milestone so we can track the work.