You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure if we want the "Trace Bridge" and "OpenCensus-Metrics-Shim" to be contained in a single Go module.
The components have different dependencies (mainly OTel Trace API vs OTel Metrics SDK).
Maybe we should provide opencensustrace (or octrace) and (or ocmetric) Go modules in subdirectories? I am leaning towards oc* package naming as opensensus will be already in the import path. Therefore, I propose go.opentelemetry.io/otel/bridge/opencensus/octrace and go.opentelemetry.io/otel/bridge/opencensus/ocmetric.
The current approach seems compliant with the OTel Specification. However, it does not follow the way we structure Go modules.
The text was updated successfully, but these errors were encountered:
This kind of a breaking change will affect these 20 known projects adversely
This will require 3 releases to complete and then stabilize the OC bridge
Split into new modules and deprecate the old
Remove the old module
Make an RC
Given the lack of motivation by most contributors for this change (and slight apprehension). There needs to be a leader with a strong desire to make this change that will put in the effort to achieve this.
I am not sure if we want the "Trace Bridge" and "OpenCensus-Metrics-Shim" to be contained in a single Go module.
The components have different dependencies (mainly OTel Trace API vs OTel Metrics SDK).
Maybe we should provide
opencensustrace
(oroctrace
) and (orocmetric
) Go modules in subdirectories? I am leaning towardsoc*
package naming asopensensus
will be already in the import path. Therefore, I proposego.opentelemetry.io/otel/bridge/opencensus/octrace
andgo.opentelemetry.io/otel/bridge/opencensus/ocmetric
.The current approach seems compliant with the OTel Specification. However, it does not follow the way we structure Go modules.
The text was updated successfully, but these errors were encountered: