Linked to upstream - https://github.com/eclipse/che/issues/17307

[Milestone 1 - MVP support of Devfile v2](https://github.com/eclipse/che/milestone/136)
Deploy Che and the DevWorkspace controller using chectl server:deploy --workspace-engine=dev-workspace
Support factory link that points to a git repo with a devfile 2.0 (WITHOUT plugins). Theia, machine exec, route class are implicitly added by Che.
CheTheia doesn’t use Che server API anymore but reads workspace info it needs from DevWorkspace / cluster resources directly
Dashboard provides the list, status, progress of DevWorkspaces
Updates to the devfile model to support ephemeral and asynchronous volumes
Documentation updates to include DevWorkspace engine support
Setup of the DevWorkspace version of the Happy path e2e test
Initially supported namespace strategy: per user
Initially supported PVC strategy: common
Single host routing supported only
Workspaces are not authenticated (anyone with the URL has access)
Not compatible with the Web Terminal operator

[Milestone 2 - Support for editors plugins and samples stacks, compatible on cluster with WTO](https://github.com/eclipse/che/milestone/139)
he following features are included in this milestone:

Che Theia Plugins support
In the plugin registry, Che-Theia Plugins definition should be in the Devfile format
The Dashboard should be able to get the definition of a theia plugin and create the corresponding DevWorkspaceTemplate
The DevWorkspace controller should be able to reconcile a DevWorkspace with a plugin that points to a DevWorkspaceTemplate (PR devfile/devworkspace-operator#240)
Devfile registry should use v2 devfiles
Create a v2 Devfile for every sample we currently have
Include a v2 Devfile in the sample repositories that we own
Update the Devfile registry with the v2 devfiles and, when the devfile is in the repo, with only the link to the git repository
It should be possible to install Che and OpenShift Web Terminal on the same cluster
Che with devfile v2 support run on Kubernetes (minikube)
The following are not:

Auth for workspaces (whoever guess the URL gets in)
Support for override vsx extension sidecar (for example run it in theia or in user user containers)
Use of the new devfile registry (used by odo)
No parents support
No GitHub/GitLab/BitBucket and private repositories support
Support for OpenShift 3.11 and 4.4 or lower

[milestone 3 - Che server and DevWorkspace engines feature parity](https://github.com/eclipse/che/milestone/140)
Merge Che-Theia and machine exec
Support trusted certificates bundles
Support custom TLS certificate for Che ingress
Support injecting secrets in workspaces (maven settings, ssh keys, git credentials…)
Theia manages .vscode/extensions.json recommendations files
Include in Che Dashboard some getting started example with vscode extensions
Multi-host support
Ephemeral and asynchronous storage (implementation)
DevWorkspace operator is published on the OperatorHub
No devfile use case support
DevWorkspace devfile parent and other v2 features support
Che multi cluster support using one DevWorkspace` operator per cluster