[tracking] Release 1.9

[pavolloffay]

Creating this to track release 1.9. Please post issue which we want to include in the release or point out breaking changes for documentation.

• gRPC Use Protobuf and gRPC for internal communications #773
• archive traces for Elasticsearch Support archiving traces with ES storage #818
• Bump UI with trace graph
• Bump jaeger lib to 2.0 - optional, jaeger go client has to be updated too

[yurishkuro]

We may need a smaller scope than #773, eg we don't have to block on not finishing up the JSON APIs.

[pavolloffay]

I mainly wanted to stabilize post spans service so we can start doing some work in clients. We can break it down into separate issues.

[objectiser]

@yurishkuro Would have been good to get jaegertracing/jaeger-ui#276 in - but not sure how close it is.

[pavolloffay]

@objectiser @yurishkuro do we want to bump also jaeger lib to 2.0 in this release?

[yurishkuro]

I'm fine either way. It only makes sense to bump it if we actually implement the metrics descriptions.

[objectiser]

Was hoping to have for 1.9 but should probably slip to 1.10 as would also need release of go client and resolve the Prometheus version

[pavolloffay]

thanks for the responses.

The main blocker is still #818. It would be great to get a review of that PR.

So if the client is updated with the latest lib version before #818 is merged we can include, otherwise, do not block on it.

[pavolloffay]

We would like to release early on Monday. Before the release I will bump the UI @tiffon promised to release it before.

The only outstanding issues are

• Change index prefix from : to - #1284
• Support archive traces for ES storage #1197 (optional)

[yurishkuro]

#1283 needs to be added to the changelog