bad jaeger tagged release

[lizthegrey]

https://pkg.go.dev/mod/go.opentelemetry.io/otel/exporter/trace/jaeger@v1.0.0?tab=versions

we incorrectly created v1.0.0 on November 4 and now Go module proxy has cached it.

we should investigate whether we can get it purged.

[jmacd]

@marwan-at-work says this is permanently cached in the Go team's checksum database, which is a security mechanism for Go modules. We may have trouble re-using this tag.

[lizthegrey]

this also causes someone running go get -u [...] to pull the bad version as it's the "latest"...

[ferhatelmas]

Relevant issue - golang/go#34189

I asked for the clarification of this case in a comment.

[lizthegrey]

golang/go#24031 probably would resolve this issue by allowing us to badlist the v1.0.0 release.

[paivagustavo]

We should probably look for a workaround for this since there is no clear solution other than waiting for version v1.0.1 to come out. People are starting facing issues because of this. Some examples of the people that faced this:

• Found the error go.opentelemetry.io/otel/sdk/export for opentelemetry with jaeger exporter #470
• https://gitter.im/open-telemetry/community?at=5e41add23716b919ba0d5824

One possible solution that I have suggested on gitter is renaming the package, that should fix the problem.

[wingyplus]

@paivagustavo how about go get jaeger module with goproxy direct mode for now until this lib reach 1.0.0?

[lizthegrey]

agree renaming package makes good sense.

[MrAlias]

I'm planning to go with the suggestion made in the 2020-02-13 SIG meeting:

Suggestion was to rename the “exporter” part of the URL to “exporters”. This would affect all the exporters, but given the alpha state it seemed reasonable.

Unless there is an alternate naming suggestion.

[lizthegrey]

Agree, good idea.