-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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.
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
Release 1.10 #1321
Comments
Please add what you want to include in the release cc) @jaegertracing/jaeger-maintainers |
Can we have #1312 in this release? |
@annanay25 if it is merged sure. It seems more like a refactoring for #1307 which probably won't make to 1.10 or do you need it in 1.10? |
In this release we introduce archive storage for ES. At the moment ES storage factory fails if it cannot connect to ES - this effectively means that it will fail when upgrading to 0.10 from an older version. We should introduce the following flag to enable archive storage. This is already done for C*
|
@yurishkuro could you please have a look at #1348 and also merge #1328. We would like to do the release this week. We need latest changes in the operator. |
We have all issues for the release resolved I will prepare for the release and cut it today or on Monday |
I'd like to understand what's with the UI, thwre may be features we want to release. |
There is only one commit since the last UI release and the new UI hasn't been released. |
The images had been pushed but binaries are not uploaded https://travis-ci.org/jaegertracing/jaeger/builds/493823895. I will have a look at this on Monday morning. |
It seems that use wasn't build in but |
Actually the build was fine the assets are uploaded https://github.com/jaegertracing/jaeger/releases. The are failed jobs because
runs for every job even whern DEPLOY=false. We should add check on deploy env var on that line. |
|
Closing all has been done. |
Tracking issue for release 1.10
The text was updated successfully, but these errors were encountered: