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.

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

Closed
4 tasks done
pavolloffay opened this issue Feb 8, 2019 · 13 comments
Closed
4 tasks done

Release 1.10 #1321

pavolloffay opened this issue Feb 8, 2019 · 13 comments
Assignees

Comments

@pavolloffay
Copy link
Member

pavolloffay commented Feb 8, 2019

Tracking issue for release 1.10

@pavolloffay
Copy link
Member Author

Please add what you want to include in the release

cc) @jaegertracing/jaeger-maintainers

@annanay25
Copy link
Member

Can we have #1312 in this release?

@pavolloffay
Copy link
Member Author

@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?

@pavolloffay
Copy link
Member Author

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*

 --es-archive.enabled                                 Enable extra storage

@pavolloffay
Copy link
Member Author

@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.

@pavolloffay
Copy link
Member Author

We have all issues for the release resolved I will prepare for the release and cut it today or on Monday

@ghost ghost assigned pavolloffay Feb 15, 2019
@ghost ghost added the review label Feb 15, 2019
@yurishkuro
Copy link
Member

I'd like to understand what's with the UI, thwre may be features we want to release.

@ghost ghost removed the review label Feb 15, 2019
@pavolloffay
Copy link
Member Author

There is only one commit since the last UI release and the new UI hasn't been released.

@pavolloffay
Copy link
Member Author

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.

@pavolloffay pavolloffay reopened this Feb 15, 2019
@pavolloffay
Copy link
Member Author

It seems that use wasn't build in make build-all-platforms && bash ./scripts/travis/package-deploy.sh

but build-all-platforms does not depend on build_ui

@pavolloffay
Copy link
Member Author

Actually the build was fine the assets are uploaded https://github.com/jaegertracing/jaeger/releases. The are failed jobs because

before_deploy:
  - make build-all-platforms && bash ./scripts/travis/package-deploy.sh

runs for every job even whern DEPLOY=false. We should add check on deploy env var on that line.

@pavolloffay
Copy link
Member Author

pavolloffay commented Feb 15, 2019

  • Update docs

@pavolloffay
Copy link
Member Author

Closing all has been done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants