-
Notifications
You must be signed in to change notification settings - Fork 57
Make Che 7 default on che.openshift.io #994
Comments
Blocked by eclipse-che/che#11664 |
@ibuziuk : That is something we should get done before the end of K train.
Don't make those default yet. The idea would be to start testing them and getting tests on that. We can also prepare the different code samples and get some docs written. |
@slemeur you mean sprint, not train right ?
Do you mean that for some period of time there should be 2 version of stacks for the same technology e.g. |
Yes I think so.
…On Tue, Oct 23, 2018 at 12:15 PM Ilya Buziuk ***@***.***> wrote:
I would start by introducing few of the new stacks (probably next train):
you mean sprint, not train right ?
Don't make those default yet. The idea would be to start testing them and
getting tests on that. We can also prepare the different code samples and
get some docs written.
Do you mean that for some period of time there should be 2 version of
stacks for the same technology e.g. go-default and go-che7 ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#994 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABj5odDxbH2YmyaQGJcj18Ui5kzOGmZ_ks5unuxbgaJpZM4XwqC5>
.
--
Stévan LeMeur // Product Manager // Developer Tools // +336-87-11-27-55
|
It makes more sense that the team that are working on the Plugin API for these LS (IDE 2 and Languages) create the stack too. |
On this issue it is important that we consider the code samples that we are providing with the stacks. |
Should be closed once we promote Che 7 GA on prod - #1490 |
Closing in favour of #1490 |
Turn all the stacks/projects on rh-che (che.openshift.io) to use the new IDE and workspace mechanisms. We need to leave only the stacks used from the regular OSIO flow on Che6 for now.
The text was updated successfully, but these errors were encountered: