Gerhard Stöbich

> Breaking for SDK implementers. SDKs must implement the attach/detach methods. Created https://github.com/open-telemetry/opentelemetry-js/pull/2531 to avoid automatic breaking of the OTel SDK.

A `detach` happens automatically if the current JS tick function ends. So it might be correct to not call detach if you want the context active until the resource vanishes....

Does this really solve a problem? If there is all noop it's don't care if we return ROOT_CONTEXT or NOOP_CONTEXT as the Tracer in question is a NoopTracer. If we...

> @Flarna there is no chance for the user to pass a context to be used for an export. We could create a `ManualSpanProcessor` for this usecase to be used...

> Does it make sense to "try" to fullfill anyway since we know its almost impossible ? Well, I think it depends on the actual use case. Supporting this alone...

I think we should at least update our samples to never pass a `TracerProvider` around without really needed. e.g. `registerInstrumentation()` perfectly picks up the global `TracerProvider` so there is no...

I'm also unsure. If we change it we have to at least enable it [here](https://github.com/open-telemetry/opentelemetry-js-api/blob/504041a8aa8442987a95f675af0a402084678682/src/api/context.ts#L26). I did a fast look into Java and Python and it seems they instantiate and...

I think the https://github.com/open-telemetry/opentelemetry-js-api/pull/97 was on a good path. My main concern were the non backward compatible changes there which should be fixable. Personally I have no special opinion if...

Is there already a deprecation workflow defined? For example node.js has [3 types of deprecations](https://github.com/nodejs/node/blob/master/doc/guides/collaborator-guide.md#deprecations) where doc deprecated is the only one which is not semver major.

> 2\. In the next major release, all previously `@deprecated` functions are removed. This will likely be much later. Maybe we should add also a minimum timeframe for removing, or...