[tracking] Patch release 1.17.1

[yurishkuro]

• Kafka TLS (Breaking change in v1.17.0 when using to Kafka + TLS #2092)
• UI may not have been released correctly (search.maxLimit is not working in UI jaeger-ui#532)

[jpkrohling]

Possibly #2094 too?

[pavolloffay]

Do we want to release from release branch or master? Since the release we have migrated go modules.

[yurishkuro]

I prefer to release from master. Go modules is not a breaking change.

[pavolloffay]

In master there are couple of breaking changes. We will have to relase from release branch. I have created release-1.17 after migration to go modules and proto generation refactoring by @annanay25. I have also backported the TLS fix.

https://github.com/jaegertracing/jaeger/commits/release-1.17

Now the UI fix has to be merged and UI released and updated here.

[objectiser]

@yurishkuro Could we also get jaegertracing/jaeger-ui#542 included in the UI release?

[pavolloffay]

All blocking PRs have been merged. We can proceed with the release. We need a patch release of the UI (1.7.1) and bump it here.

[pavolloffay]

Release UI jaegertracing/jaeger-ui#543

[pavolloffay]

We should agree and document when the changelog should be updated. I don't find it very useful to update it for patch releases. It adds unnecessary overhead.

[objectiser]

I think the fixed bugs need to be documented atleast on the GH release page, and may be add to the CHANGELOG for the next minor release?

[yurishkuro]

I don't think we should diverge GH releases and the changelog. What's the downside of adding a patch release to the changelog?

[pavolloffay]

Release job https://travis-ci.org/github/jaegertracing/jaeger/builds/661867156?utm_medium=notification&utm_source=github_status