Update the OpenTelemetry SDK version to 1.35.0 and remove jaeger exporter

[laurit]

Backport of #10455 and #10241

[trask]

is removing jaeger exporter necessary? would be nice not to do that in a patch release if we don't have to

[laurit]

is removing jaeger exporter necessary? would be nice not to do that in a patch release if we don't have to

Jaeger exporter was removed from sdk. That leaves us the following options

• remove jaeger
• not update sdk
• include the latest jaeger exporter and hope that it works with the latest sdk

[trask]

I think my preference would be to not update the SDK in that case.

@jack-berg @jkwatson any thoughts? thanks

[jkwatson]

I think my preference would be to not update the SDK in that case.

@jack-berg @jkwatson any thoughts? thanks

No opinion from me. I don't use the agent, and now I don't use the Jaeger exporters, either. ;)

[trask]

another option would be to bump the version to 1.36.0 (creating a new release/v1.36.x branch)

[jack-berg]

Creating new 1.x release branches which mirror opentelemetry-java releases is interesting..

I'm also open to publishing patch releases for 1.34.x for security vulnerabilities until instrumentation's support for 1.x ends. I recall that semconv requires >= 6 months of support. Is there a specific support time period in mind for 1.x?

[trask]

another option would be to bump the version to 1.36.0 (creating a new release/v1.36.x branch)

oops, I meant 1.33.0 (creating a new release/v1.33.x branch)

[trask]

I recall that semconv requires >= 6 months of support. Is there a specific support time period in mind for 1.x?

I think we're open to security patching 1.x for longer than 6 months if there's demand

[trask]

I re-targeted this to the new release/v1.33.x branch