Jack Berg

Resolved in #4231.

Reopening this since we reverted the fix in #4736. Need to wait for a resolution on spec PR [#2770](https://github.com/open-telemetry/opentelemetry-specification/pull/2770).

The spec has [changed](https://github.com/open-telemetry/opentelemetry-specification/pull/2770/files) the default boundaries to `[ 0, 5, 10, 25, 50, 75, 100, 250, 500, 750, 1000, 2500, 5000, 7500, 10000 ]`. Note that the only difference...

This was resolved in #2676. There's now [explicit text](https://github.com/open-telemetry/opentelemetry-specification/blame/main/specification/logs/api.md#L52-L54) stating: > Normally, the LoggerProvider is expected to be accessed from a central place. Thus, the API SHOULD provide a way...

Closing now that there is an official [opentelemetry-android](https://github.com/open-telemetry/opentelemetry-android) project.

Closing as "wontfix" because sufficient time has passed and there are no additional details.

Bumping this given the desire to stabilize the OT shim. Do the current tests have the required coverage or is more needed?

Closing as I believe this is not needed. The [opentracing shim spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/opentracing.md) is stable and says that spancontext and baggage are included in the context. @carlosalberto feel free to re-open...

The jaeger exporters were removed in #6119 so this is no longer relevant.

A JMX metric exporter is outside of the defined [project scope](https://github.com/open-telemetry/opentelemetry-java/blob/main/CONTRIBUTING.md#project-scope). If you still have interest in this, consider contributing it to `opentelemetry-java-contrib`.