Daniel Dyla

> > @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...

This infinite loop is fixed in recent API versions

per-package namespaces are great but there might be value in a host prefix too.

We now have a component logger. If that doesn't solve your use case please open an issue in https://github.com/open-telemetry/opentelemetry-js as the API package is moving there

@secustor can you please re-apply this in https://github.com/open-telemetry/opentelemetry-js where this package is now moved?

I think this would be a breaking change and isn't something we've had people asking for so I'm going to close it.

In a minor version bump, it is acceptable to introduce changes which break interface compatibility with the SDK, requiring the SDK to implement the change in the next version. It...

Personally I think if we want to include this feature we should do it in such a way that at least it doesn't break existing SDK, even if the feature...

Personally I think it would be good to include this if we can get the work done in time. @longility would you volunteer to add this (or @vreynolds)? It would...

There are SDKs "in the wild" that depend on API `^1.0.x` ([example](https://github.com/open-telemetry/opentelemetry-js/blob/stable/v1.0.0/packages/opentelemetry-sdk-trace-node/package.json#L62)) which still receive significant downloads. These SDKs could break if someone calls `recordException(exception, attributes, time)` when they are...