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

Che 7 Beta #12170

Closed
41 of 69 tasks
slemeur opened this issue Dec 11, 2018 · 4 comments
Closed
41 of 69 tasks

Che 7 Beta #12170

slemeur opened this issue Dec 11, 2018 · 4 comments
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed.

Comments

@slemeur
Copy link
Contributor

slemeur commented Dec 11, 2018

Che 7 Beta Details

Goal: The implementation of the new capabilities for Che 7 has been targeting the self-hosting mode from its start. The goal of the Che 7 Beta, is to finalize the new Che version with the ability for everyone to use Eclipse Che to extend/customize it. That version will also include the first part of a new CLI which simplify the installation and management of Che.

User Story 1 (hosted theia plugin dev): As a Che developer I want to start a ws.next based workspace that is configured to load theia as the editor and an “hello world” frontend theia plugin (using an existing che stack from the dashboard and with the editor and plugins definition available in a remote plugin registry) so that I will be able to easily extend this model developing new theia plugins.

User Story 2 (java/nodejs dev): As a developer using Che, I want to start a ws.next based workspace that is configured with the tooling that I defined for my NodeJS/Java project (configuring it from the dashboard, or using a devfile on the repository) so that I will be able to develop on my project and get all language tooling.

User Story 3 (chectl and operator): As an admin of Che, I want to use a CLI based tool that is provided with Che to install and configure my Eclipse Che using (using the operator) so that I can easily control my installation.

User Story 4 (k8s plugin basic flow): As a developer using Che, I want to interact with my K8S / OpenShift cluster using dedicated plugins, so I can manage my cluster and push my source code onto the cluster.

Success Criteria:
Implementation of the 4 user stories with:

  • The plugin registry is deployed with the plugin viewer
  • The user is able to configure the workspace for his project with the tools he wants
  • Complete inner loop is working in the new IDE: Code, Build, Run and Debug
  • Java and NodeJS Supported (including Debugger)
  • Complete support of K8S objects into workspaces
  • Installation flow managed from the CLI

What's in Che 7 Beta:

  • Workspace.Next finalization: Support all K8S objects
  • IDE.Next: Plug-ins API and support for Java, Typescript, XML, YAML
  • Plugin Broker
  • DevFile Support
  • Introduction of a new CLI
  • Che-in-Che development
  • Introduction of tests for Theia IDE
  • Minimal experience refinements (Terminal, Dashboard, Configuration)
  • Minimal set of documentation

What's not in Che 7 Beta:

  • Implementation of a new dashboard to better fit with Workspace.Next and devfile changes
  • Go, Python, PHP Support
  • Pull Request plugin
  • Complete CLI

Target: 5th February

Che 7 Beta Sub-tasks

Che OSIO

IDE

IDE 2

Languages

Platform

Deploy

Docs

  • Get Started with Eclipse Che 7 RHDEVDOCS-917
  • User How-to: Create a workspace from code sample
  • User How-to: Create a workspace by import source code of your project
  • Che Workspaces outline
  • Creating Eclipse Theia Plug-ins with Eclipse Che outline
  • Extending How-to: How to Add Support for a new language outline
  • Extending How-to: How to Add Support for a new debugger outline
  • Extending How-to: How to switch the default editor from Che, to another one outline
  • Update the readme.MD and customizing.MD with the new information about Che-in-Che outline

Others

Che 7 GA Sub-tasks

IDE2

IDE

Languages

Platform

QE

@slemeur slemeur added the kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. label Dec 11, 2018
@garagatyi
Copy link

@slemeur what if we also create Che GA epic and put there everything we want for the GA to keep track of the stuff?

@skabashnyuk skabashnyuk pinned this issue Dec 14, 2018
@SkorikSergey SkorikSergey unpinned this issue Dec 17, 2018
@SkorikSergey SkorikSergey pinned this issue Dec 17, 2018
@dmytro-ndp dmytro-ndp unpinned this issue Dec 17, 2018
@vparfonov vparfonov pinned this issue Dec 21, 2018
@gazarenkov gazarenkov unpinned this issue Dec 22, 2018
@gazarenkov gazarenkov pinned this issue Dec 22, 2018
@vinokurig vinokurig unpinned this issue Jan 3, 2019
@garagatyi
Copy link

@ibuziuk @l0rd our team finished parts of Improving the Plugin Broker (WIP) #11980 that were needed for the beta/GA. Should we mark it as done?

@slemeur
Copy link
Contributor Author

slemeur commented Jan 14, 2019

sure go ahead!

@garagatyi
Copy link

Since Florent self-assigned #12292 I moved it from others section to IDE2 team section which used to accommodate Florent's issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed.
Projects
None yet
Development

No branches or pull requests

3 participants