Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Release 1.18.0 #2236

Closed
pavolloffay opened this issue May 11, 2020 · 4 comments · Fixed by #2244
Closed

Release 1.18.0 #2236

pavolloffay opened this issue May 11, 2020 · 4 comments · Fixed by #2244
Labels
meta-issue An tracking issue that requires work in other repos
Milestone
Release 1.18

Comments

@pavolloffay
Copy link
Member

The tracking issue for release Jaeger 1.18.0

Release commit history: v1.17.1...master

This release should include jaeger-ui 1.9.0 - the release has to be done.

@jaegertracing/helm-charts-maintainers please list any outstanding issues that should be included in jaeger or jaeger-ui for this release.
@pavolloffay pavolloffay added the meta-issue An tracking issue that requires work in other repos label May 11, 2020
@pavolloffay pavolloffay added this to the Release 1.18 milestone May 11, 2020
@ghost ghost added the needs-triage label May 11, 2020
@pavolloffay
Copy link
Member Author

If there won't be any concerns I would like to get the release out before Wednesday 13.5.

@naseemkullah
Copy link
Member

I think you meant to cc jaeger maintainers not the charts maintainers @pavolloffay ?

@pavolloffay
Copy link
Member Author

yes cc @jaegertracing/jaeger-maintainers

@yurishkuro
Copy link
Member

I think we should include #2242, because without it PR #2090 results in confusing behavior.

@pavolloffay pavolloffay mentioned this issue May 14, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
meta-issue An tracking issue that requires work in other repos
Projects
None yet
Milestone
Release 1.18
Development

Successfully merging a pull request may close this issue.

Preparing release v1.18.0 pavolloffay/jaeger
3 participants
@yurishkuro @pavolloffay @naseemkullah