Che 7 GA

[l0rd]

Che 7 GA Details

Schedule

• 05/22 - Che 7 RC1: Che 7 features completion
• 06/12 - Che 7 RC2: Bug Fixes / Documentation / Test automation
• 07/03 - Che 7 GA (this may change)

Goal: Release the new version of Che 7 in a GA state, including documentation, automated tests and website updates.

User Story 1 (hosted theia plugin dev): As a Che developer I want to start a workspace 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 developing new plugins.

User Story 2 (java/nodejs dev): As a developer using Che, I want to start a 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 (k8s developer experience): As a developer working on a K8S application, I want to be able to use the definition of my application (yaml) in order to create a devfile and get a developer workspace for Che which will replicate my application to allow fast iterative development.

User Story 4 (chectl and operator):

• As an admin of Che (or user using Che locally), 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.
• As an admin (or user using Che locally) of a kubernetes cluster, I want to use the OperatorHub to proceed the installation of Eclipse Che.

User Story 5 (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.

User Story 6 (mutli-editors experience):

• As a developer using Che, I want to build my application using my IDE where I can build code and debug it. I can deploy my application onto K8S / OpenShift cluster using dedicated plugins.
• As a different persona (data scientist), I can work on the same application/context with adapted tools for my needs (Jupyter).

Che 7 Success Criteria:
Implementation of the 5 user stories with:

• 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
• Devfile has the only format exposed to define workspaces (stacks, factories)
• Languages: Java, Node, Typescript, XML, YAML, C#, Go, Python, PHP
• Out of the box stacks and samples updated
• Chectl as a new CLI for Che
• UX refinements for installation of plugins
• UX adaptations in dashboard to cover devfiles and other che 7 new capabilities
• Ability to switch editors
• Easier monitoring and tracing capabilities
• Pull Request plugin

Subtasks

BUGS:

We are using the following label to list all the bugs that need a fix for Che 7 GA.
Link to the GitHub request: Che 7 GA Bugs

UNASSIGNED

• Self-signed certs support (Che 7, TLS and self signed certs #12634)

IDE2

• Bug fixing
  • Setting commands path doesn't work (Make it possible to specify path for command execution in its configuration #11866)
  • Plugin Preference Schemas are ignored (#4773) PR
  • Sometimes plugins are not loaded the first time (https://github.com/eclipse/che-theia/issues/101)
  • New Terminal" opens unresponsive terminal window ("New Terminal" opens unresponive terminal window #13030)
  • Add VS code extensions preferences in workspace configuration (Add VS code extensions preferences in workspace configuration #12992)
  • Rename container view (Rename containers view #12984)
  • Handle plugins with no activate function #4850
• Dashboard: remove Plugins/Editors from "create workspace" panel (Dashboard: Remove plugins and editors lists from workspace creation page #12896)
• Plugin installation UX (Plugin Installation UX #12905)
• Sharing from the IDE (Sharing from the IDE #12722)
• Detect services that are listening to a port (On the go workspace config: detect if a service that is listening to a port and propose to expose it #12061)
• Dashboard: cleanup "edit workspace" panel (Dashboard: Simplify workspace edition tabs #12909)
• Dashboard respect Devfile:
  • [UD] Workspace creation from devfile [UD] Workspace creation from devfile #13058 PR
  • [UD] Allow user to manage workspace devfile [UD] Allow user to manage workspace devfile #13067
• Make Theia respect Devfile field of Workspace Make Theia respect Devfile of a field of Workspace #13112
• Adapt WorkspaceLoader to workspaces created with Devfile Adapt WorkspaceLoader to workspaces created with Devfile #13201
• Dashboard: mark with an error old Che 6 workspaces (Dashboard: Display error mark about Che 6 workspaces #12917)
• Handle Che 7 incompatible factories (Handle incompatible Factories between Che 6 and Che 7 #12918)
• Handle memory configuration (Include sidecars memory into total memory of workspace on dashboard #11801) => blocked by OSIO's Merge all che_plugin.yml fields into meta.yaml  #12908
• Dashboard, don't display the list of sample plugins by default (Dashboard : Should not display the list of sample plugins #12910) => should be handled by OSIO's #55

IDE

• Bug fixing:
  • Can not run Configured task Can not run Configured task eclipse-theia/theia#5064
  • Recently used tasks section should respect configured tasks Recently used tasks section should respect configured tasks eclipse-theia/theia#5067
  • Contributed Task Configuration question Contributed Task Configuration question eclipse-theia/theia#4928
  • Provide curated list of containers to run tasks Provide curated list of containers to run tasks #13390
  • Notifications on Tasks started/ended are missing context Notifications on Tasks started/ended are missing context #13394
  • Error running a task/che-commands (running a task/che-commands is showing error: Request {taskname} failed with error: Information not found che-theia#155) [NEW]
• wsmaster scalability issues: Output Endpoint (Che Server rejects JSON RPC messages which may lead to losing events #11961)
• Che commands should be first class citizens in Theia (Commands/tasks/launch and workspace configuration synchronization #12709):
  • Export commands as task.json (User defined Che tasks commands should be exported in a tasks.json file #12712) [WIP] PR
  • Export debug commands as launch.json (Che commands should be of type task or launch #12710 and User defined Che launch commands should be exported in a launch.json file #12711) [WiP] => Design document
• Finalize Kubernetes Plugin Support (Add Theia Plugin APIs to support VS Code Kubernetes Tooling  #10574) [WIP] => Already in Che plugin registry [Status document] (https://docs.google.com/spreadsheets/d/1TflFxsQyhySONi63UrHYLbACwVxo8Upq9zOCiFatHG4/edit#gid=667279502) we consider this task like done
• Finalize OpenShift Plugin Support (Add Theia Plugin APIs to support VS Code OpenShift Tooling #11488) [WIP]=> Already in Che plugin registry Status document
• Rework Task extension to a plug-in ([Theia][Plugin]Rework Task extension to Task plugin #11458) [WIP] merged PR
• Integration of the GitHub Plugin (Include existing GitHub plugin in Che Theia IDE #11867) [WIP]
• Extend pull request flow to add Factory in the comments (Extend GitHub VSCode Extension to integrate Pull Request Review Flows #10282)

Languages

• Bug fixing:
  • Filesystem privileges issues when bootstrapping JDT LS (Plugin doesn't launch after adding it to the workspace #12904)
• VSCode Java Debug support (Che 7 plugin: vscode-java-debug #12446 and Support running multiple VS Code extensions in the same sidecar #12395)
• Test Language Support Plug-ins on Minishift (Test Language Support Plug-ins on Minishift #12941)
• Python support:
  • Integration of Python (Che 7 plugin: Python  #12771)
  • Python Stack (Python Stack #12944)
  • Django Stack (Django Stack #12945)
• C# support:
  • Integration of C# - Che 7 CSharp support #12773
  • C# Stack C# Stack #13096
• PHP support:
  • Integration of PHP (Che 7 plugin: PHP Language Support #12772)
  • PHP Stack (New Che 7 Stacks #12620)
• Camel support:
  • Integration of Camel Plugin (Camel Plugin for Che 7 #12584)

OSIO

• Enforce a better plugin registry naming convention Naming convention che-plugin-registry#55 [Done in 7 beta 4]
  • Adapt chectl to new plugin notation che-incubator/chectl#89
  • Adapt to new plugin notation redhat-developer/rh-che#1390
• Merge meta.yml and che-plugin.yml - Merge all che_plugin.yml fields into meta.yaml  #12908 [Done in 7 beta 5]
  • Merge meta.yaml and plugin yaml in v3 che-plugin-registry#135
  • Process additional fields in meta.yaml redhat-developer/rh-che#1308
  • Update version of registry and plugin broker on wsmaster side to catch up regitry / broker changes - Configure new plugin registry and broker #13311
• VS Code marketplace rate limit - VS Code marketplace rate limit error #12840 [WORKAROUND PROVIDED]
• Allow to use 'latest' for plugin versions Allow to specify 'latest' version of plugins in workspaces definitions #12937 Sprint: 166
  • Need to create the latest folder for each plugin in the plugin registry that would allow to specify plugins with the latest version redhat-developer/rh-che#1395
  • NOT PLANNED FOR GA If the plugin version is not specified - fall back on latest  redhat-developer/rh-che#1396 PR sent WIP Make plugin references without version use 'latest' implicitly #13414 but conflicts with Add possibility to specify reference or registry url for chePlugin/cheEditor type components #13297
• Support running multiple VS Code extensions in the same sidecar Support running multiple VS Code extensions in the same sidecar #12395
• Avoid the need to set userland-proxy Avoid the need to set userland-proxy #11018 Sprint: 166
• Implement compatibility with the new automatic multicast discovery in plugin broker Implement compatibility with the new automatic multicast discovery in plugin broker redhat-developer/rh-che#1354 Sprint: 166
• Telemetry - Integrate Che7-compatible workspace telemetry, and extend it to meet Upstream Che needs #12717 Postponed after Che 7 GA
• Bug fixing:
  • Use upstream che 7 stacks as-is in rhche without any customizations Use upstream che 7 stacks as-is in rhche without any customizations redhat-developer/rh-che#1347
  • Most public images do not work as the base for Che 7 workspaces on OpenShift Most public images used in devfile registry do not work as the base for Che 7 workspaces on OpenShift #13454
  • Need to make sure that all devfiles from registry work on che.openshift.io Need to make sure that all devfiles from registry work on che.prod-preview.openshift.io redhat-developer/rh-che#1434
  • '?' folder is created when building console-java-simple project using java-maven Che 7 stack '?' folder is created when building console-java-simple project using java-maven Che 7 stack #13451
  • Workspace failed to start because of plugins installation process failed Workspace failed to start because of plugins installation process failed #12999 NO STEPS TO REPRO

Platform

• Add more fields to the plug-in registry - Handle more metadatas for the plugin viewer che-plugin-registry#71
• Finalize Devfile - Support Devfile format to generate a workspace #11549
  • Provide database layer storage and integrity of devfile as part of workspace | Provide database layer storage and integrity of devfile as part of workspace #13075 Sprint: 165
  • Add an ability to use Devfile as workspace configuration as alternative to WorkspaceConfig | Add an ability to use Devfile as workspace configuration as alternative to WorkspaceConfig #13079 Sprint: 165
  • Perform schema and integrity validation on creating a workspace from Devfile Perform schema and integrity validation on creating a workspace from Devfile #13315 Sprint: 167
  • [POC] tasks and launch configuration as part of Devfile | [POC] tasks and launch configuration as part of Devfile #13057 Sprint: 166
  • Set memory limit for sidecar plugins on devfile | Set memory limit for sidecar plugins on devfile #12981 Sprint: 165
  • Introduce registryUrl field for cheEditor/chePlugin components | Introduce registryUrl field for cheEditor/chePlugin components #13104 Sprint: 167
  • Rename name field of component to Devfile to alias | Rename name field of component to Devfile to alias #13103 Sprint: 165
  • Adopt devfile format for Stacks - Adopt devfile format for Stacks #12924 Sprint: 167
    • Initial setup of Che Defvile registry | Initial setup of Che Defvile registry #13353 Sprint: 167
    • StackService decommissioning StackService decommissioning #13459 Sprint: 167
    • Che 7 stacks should use version "latest" of plugins Che 7 stacks should use version "latest" of plugins #13426
    • Deploy and use public che devfile registry on https://che.openshift.io infrastructure Deploy and use public che devfile registry on https://che.openshift.io infrastructure #13355 Sprint: 167
  • Adopt devfile format for workspaces(API part) - Adopt devfile format for workspaces configuration #12926 Sprint: 165
  • [POC] Devfile format for Stack, Factory, Workspace API | [POC] Devfile format for Stack, Factory, Workspace API #13018 Sprint: 165
  • Provide database layer storage and integrity of devfile as part of workspace | Provide database layer storage and integrity of devfile as part of workspace #13075 Sprint: 165
  • Make Devfile syntax K8s-compliant Make Devfile syntax K8s-compliant #13061
    • [Devfile] Make specVersion and name more K8s-like [Devfile] Make specVersion and name more K8s-like #13336 Sprint: 167
• Finalize Monitoring - Che Monitoring #10329
  • Create documentation for monitoring use-case | Create documentation for monitoring use-case #12543 Sprint: 166
• Finalize Tracing - Che Tracing #10298
  • Document tracing usecase Document tracing usecase #12545 Sprint: 167
• Support mountSources for non-plugin tools in devfile Support mountSources for non-plugin tools in devfile #12554 Sprint: 168
• Deprecate storing of workspaces converted from Devfile Deprecate storing of workspaces converted from Devfile #13423 Sprint: 166
• Legacy environment variables cleanup Legacy environment variables cleanup #12679 Sprint: 167
• Bug fixing:
  • Error when starting workspace, created from devfile | Error when starting workspace, created from devfile #13040 Sprint: 165
  • NPE after force infrastructure restart NPE after force infrastructure restart #13313 Sprint: 165
  • GitHub oAuth authorization does not work with Red Hat SSO 7.3 GitHub oAuth authorization does not work with Red Hat SSO 7.3 #13380 Sprint: 167
  • Workspace is not starting, when k8s StorageClass has volumeBindingMode=WaitForFirstConsumer Workspace is not starting, when k8s StorageClass has volumeBindingMode=WaitForFirstConsumer #12889 Sprint: 167
  • Volume created but the secret with the self-signed cert is not Volume created but the secret with the self-signed cert is not #13433

Installation

• Operator for Che 7 on OperatorHub (Kubernetes Operator for Che deployment #11469) - [WIP] PR1 and PR2
• chectl:
  • command server:stop
  • command server:delete
  • command devfile:generate (#81) - [WIP] PR
  • OCP support (#80)
  • Docker desktop support (#14)
  • command server:update (#32 and Update Development Workflow Documentation for Che 7 #12411))
  • Bug fixing: #18, #82, #78

QE

• Define the strategy to add tests on Theia (WIP) (Investigate e2e technologies for Thea Investigate e2e technologies for Thea #12204)
• E2E tests suite for Che 7 (E2E tests suite for Che 7 #12728) - [WIP]
  • Setup the new test solution (selenium-typescript + Mocha + Chai) (Investigating new typescript related test framework #13114) - [WIP] - PR [ TS-SELENIUM ] Investigating new typescript related test framework #13200
  • Prepare yaml file for deploying test application (Nodejs+MongoDb) based on Kubernetes/Openshift infra (Prepare yaml file for deploying test application (Nodejs+MongoDb) based on Kubernetes/Openshift infra #13119) - [WIP]
  • Add PR trigger for happy path job (che7-test-ci) (Add PR trigger for happy path job #13173) - [WIP]
  • Setup periodic job to test Che started with chectl (Setup periodic job to test Che started with chectl #13229) - [WIP]
  • Configure CI for new E2E tests (Configure CI for new E2E test suite #12729)
• Scalability testing - [WIP]
• Add theia-ide/theia PR check against che.osio (Add theia-ide/theia PR check that tests against Developer Sandbox #13258)
• Add an eclipse/che nightly test against che.osio (Add an eclipse/che nightly test against che.osio #13259)
• Add eclipse/che PR check test against che.osio (Add eclipse/che PR trigger test against che.osio #13260)
• Run Happy path test as PR check on kubernetes infra (Stabilize E2E Happy path tests on kubernetes (minikube) infra in Central CI #13473)

Documentation, training and demos

• Integrate new documentation about extensibility
• Port Che6 documentation to Che 7
• Update README
• Update Contributing wiki
• Release notes for all new features
• Make some demo/workshop material (doc + short blog post + short video) github repo
  • Devfile (@sleshchenko) Added Devfile Demo che-incubator/che-demos#3
  • New multi container based workspace model
  • VS Code plugin compatibility
  • Container based development (@eivantsov)
  • chectl
  • Che operator
  • Monitoring and Tracing (@ibuziuk)
  • Editor swapping capability (@skabashnyuk)

Marketing and Promotion

• Update Eclipse Che website
  • Put links for Che 7 download / signup on the homepage
  • Create videos to demonstrate major Che 7 features (need a list)
  • Update Technology page and combine Features
  • Update Extend page
  • Update Technology page
  • Update footer links (remove Red Hat link)
  • Remove Community page and redirect URL to https://github.com/eclipse/che/blob/master/CONTRIBUTING.md
• Blog post series of major Che 7 features (need a list)
• Dave: Collect testimonials for Che 7 (user, OEM, plug-in developer)
• "Getting started with Che 7" document (part of project docs? or elsewhere?)
• Jesse: Create sample tweets to use around Che 7 release for #chetips
• Stevan/Dave: Prepare webinar to present Che 7

PR/AR

• Draft release announcement for a press release
• Prepare analyst briefing for Che 7 (if AR agrees it is a good idea)

[tsmaeder]

Discovered eclipse-theia/theia#4850 which is a possible blocker for php-debug support.

[l0rd]

@tsmaeder added in the IDE2 backlog

[l0rd]

This issue has been replaced by the endgame document #13637