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

Investigate how Che, CRW, WTO can depends on DWO #379

Closed
sleshchenko opened this issue Apr 8, 2021 · 3 comments
Closed

Investigate how Che, CRW, WTO can depends on DWO #379

sleshchenko opened this issue Apr 8, 2021 · 3 comments
Assignees
@amisevsk
Labels
sprint/current Is assigned to issues which are planned to work on in the current team sprint
Milestone
v0.4.0

Comments

@sleshchenko
Copy link
Member

Currently, WTO, Che, CRW embeds DWO resources which mean only one can be installed on the cluster.

We need to investigate the way we make them compatible, the idea is that DWO is available as a dependency for WTO, CRW, Che. But it has pretty many open questions which need to be investigated.
@sleshchenko sleshchenko added sprint/current Is assigned to issues which are planned to work on in the current team sprint sprint/next and removed sprint/current Is assigned to issues which are planned to work on in the current team sprint labels Apr 8, 2021
@sleshchenko sleshchenko mentioned this issue Apr 15, 2021
Closed
29 tasks
@sleshchenko sleshchenko added sprint/current Is assigned to issues which are planned to work on in the current team sprint and removed sprint/next labels Apr 15, 2021
@sleshchenko sleshchenko added this to the 0.4.0 milestone Apr 15, 2021
@sleshchenko

This comment has been minimized.

Sign in to view
@sleshchenko
Copy link
Member Author

Proposal from Angel about WTO + DWO + DWCO integration https://docs.google.com/document/d/1-6B1qdizqu-fI8SDwZ0sZslmepN7zQWw7fxrU4Ug35Y/edit#heading=h.778lsysexnzr

@sleshchenko
Copy link
Member Author

I believe it can be closed and we'll move forward with prototyping the proposed way to go in the scope of #407

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@amisevsk amisevsk

Labels
sprint/current Is assigned to issues which are planned to work on in the current team sprint
Projects
None yet
Milestone
v0.4.0
Development

No branches or pull requests
2 participants
@sleshchenko @amisevsk