Tyler Yahn

> For asynchronous tracking, new ParentSpan needs to be copied in CopyCtx(). > In addition, Span's life cycle should end after the Span.End() method call. > Exporter uses a snapshot...

> @MrAlias Guaranteed span release is achieved by the user. The user can guarantee that span is not used after span.end(), they can inject the span generator to achieve pool...

> > > @MrAlias Guaranteed span release is achieved by the user. The user can guarantee that span is not used after span.end(), they can inject the span generator to...

> @MrAlias Guaranteed span release is achieved by the user. The user can guarantee that span is not used after span.end(), they can inject the span generator to achieve pool...

> > > @MrAlias Guaranteed span release is achieved by the user. The user can guarantee that span is not used after span.end(), they can inject the span generator to...

> > > > > @MrAlias保证 span 释放由用户实现。用户可以保证在 span.end() 之后不使用 span，他们可以注入 span 生成器来实现 span 池。本期只是想支持注入 span 生成器并提供默认 span 生成。 > > > > > > > > > > >...

Looking into how we can preserver our custom capitalizations: https://github.com/open-telemetry/weaver/issues/415

Comment line wrapping: ~https://github.com/open-telemetry/weaver/issues/416~ https://github.com/open-telemetry/weaver/issues/364

@florianl please see https://github.com/open-telemetry/opentelemetry-go/pull/5898

I would strongly ask that we move forward with the original plan before we try to make too many changes at once. The existing application serves builds for many projects...