separate trace/metrics packages out for staggered 1.0 release #107
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #119
Because
opentelemetry-api
1.0 does not contain metrics, the trace and metrics exporters need to be split so that the trace exporter can be released as stable. The new package names areopentelemetry-exporter-cloud-trace
andopentelemetry-exporter-cloud-monitoring
(which happen to already exist on PyPI from before I merged them together last year).I am definitely open to new names, though – please add suggestions. Should they instead be
opentelemetry-exporter-google-cloud-{trace,monitoring}
? That's pretty long