Che 7.0.0 Endgame Plan

[l0rd]

Che 7.0.0 Endgame

Target is the 14th of August (this may change)

RULES

1. We release Che 7.0.0 as soon as:
   ENDGAME BUGS ARE FIXED
   ENDGAME ENHANCEMENTS ARE COMPLETED
   ENDGAME DOCUMENTATION IS AVAILABLE ON THE DOC SITE
   E2E HAPPY PATH TEST IS GREEN (STEPS 1, 3 and 4)
   CHE QE TEAM VERIFIES THAT THE RELEASE ACCEPTANCE CRITERIA ARE SATISFIED
2. Nothing should be merged to master if it's not in the endgame plan (che-x, che-theia, chectl)
3. Nothing should be added to the endgame plan if not approved by the endgame doc owners: @nickboldt, @l0rd, @slemeur, @tsmaeder and @rhopp

BLOCKERS

Bugs

• Verify and fix devfile registry images to work on openshift @ibuziuk
  • Need to make sure that all devfiles from registry work on che.prod-preview.openshift.io redhat-developer/rh-che#1434
  • Use upstream che 7 stacks as-is in rhche without any customizations redhat-developer/rh-che#1347
  • Most public images used in devfile registry do not work as the base for Che 7 workspaces on OpenShift #13454
  • Default projects provided with sample stack is not building  #13608
  • "/project" is not mount into the runtime container of the default python stacks #13594
• Verify and fix stacks language servers and debug adapters @tsmaeder
• Stabilize CI for happy path scenario Create jenkins job for checking HappyPath scenario with creation ws. from devfile. #13523 @rhopp
• Impossible to get a terminal in a workspace Impossible to get a terminal in a workspace #13584 @evidolob
• Theia doesn't work with self signed certs Make Che Theia respecting self-signed certificate #13574 @evidolob
• Issues with Theia configured and recent tasks Can not run Configured task eclipse-theia/theia#5064 Recently used tasks section should respect configured tasks eclipse-theia/theia#5067 Contributed Task Configuration question eclipse-theia/theia#4928 @vparfonov
• chectl server:start cheimage parameter has no effect on multiuser minikube --cheimage parameter has no effect during deploying Multiuser Che on minikube che-incubator/chectl#161 @benoitf
• chectl server:start fails if Che helm chart has status DELETE or DELETING Command server:start fails if che helm chart has status DELETE or DELETING che-incubator/chectl#18 @benoitf
• chectl uses deprecated method for creating workspaces from devfile Chectl uses deprecated method for creating workspaces from devfile #13623 @l0rd
• Clarify names of default stacks Clarify names of default stacks #13592 @skabashnyuk
• Preview URL not displayed while accessible Preview URL not displayed while accessible #13357 @evidolob
• Unable to set JAVA_OPTS or MAVEN_OPTS in kubernetes component of devfile Unable to set JAVA_OPTS or MAVEN_OPTS in kubernetes component of devfile #13340 @skabashnyuk
• Some Projects don't work with Java 11 based Java plugin Some Projects don't work with Java 11 based Java plugin #13547 @tsmaeder
• Remove UD "Diagnostics" because it's not working Remove UD "Diagnostics" because it's not working #13525 @ashumilova
• Che Plugins panel is broken on minishift https://github.com/eclipse/che-theia/issues/296 @evidolob
• Login using OpenShift 4.x OAuth doesn't work Login using OpenShift 4.x OAuth doesn't work #13659 @davidfestal
• Applications started with a che-commands (task) stop running on OpenShift Applications started with a che-commands (task) stop running on OpenShift #13620 @vparfonov
• Multi-user Che fails to start on minikube using helm Multi-user Che fails to start on k8s using helm #13625 @skabashnyuk
• keycloak image init containers shouldn't do post-install stuff keycloak image init containers shouldn't do post-install stuff #13870 @skabashnyuk
• SSH plugin doesn't show if generation has been successful or not SSH plugin doesn't show if the generation has been successful or not #13857 @vparfonov
• chectl workspace:start fails for multi-user Che chectl workspace:start fails for multi-user Che #13828 @benoitf
• Go sample permission denied issues with dependencies Go sample permission denied issues with dependencies #13823 @tolusha
• Annotation key is too long error when starting workspace, created from devfile Annotation key is too long error when starting workspace, created from devfile #13303 @skabashnyuk
• Tasks and Che Commands should not use "machineName" Tasks and Che Commands should not use "machineName" #13667 @vparfonov
• GitHub identity is persisted locally after log-out GitHub identity is persisted locally after log-out #13694 @ashumilova
• Can't update Che 7 in Minishift to use a newer devfile registry Can't update Che 7 in Minishift to use newer devfile registry #13676 @evidolob
• configmaps "sshconfigmap" already exists configmaps "sshconfigmap" already exists. #13873 @vparfonov
• Outputs are not avialable when using theia tasks Terminal widget is not displayed for theia tasks #13876 @evidolob

Enhancements

• New devfile based stacks should contain samples New devfile based stacks should contain samples #13529 @skabashnyuk
• GitHub PRs extension Include existing GitHub plugin in Che Theia IDE #11867 @vparfonov
• Git + SSH (generate with plugin + mount as secret) Allow Che 7 Git + SSH Flow #13494 Improve SSH plugin to be able to execute git commands via ssh #13866 SSH plugin doesn't show if the generation has been successful or not #13857 @vparfonov
• Deprecate storing of workspaces converted from devfiles Deprecate storing of workspaces converted from Devfile #13423 @skabashnyuk
• Legacy environment variables cleanup Legacy environment variables cleanup #12679 @skabashnyuk
• chectl should use new CRD based operator Chectl server:start command uses old plugin registry env var in configmap che-incubator/chectl#92 @l0rd
• Che registries (plugin+devfile) should be part of Che deployment Update Che Helm Chart: Che registries (plugin+devfile) should be part of Che deployment #13633 @skabashnyuk ([helm]
• Che registries (plugin+devfile) should be part of Che deployment (Che registries (plugin+devfile) should be part of Che deployment #13557)) @davidfestal (operator)
• Improve CI for devfile registry Need to periodically build arbitrary-users-patch images as part of the nightly che-devfile-registry ci job #13837 Improve che-devfile-registry CI #13813 @amisevsk
• Update release process to include new repositories (theia, broker, registries, chectl, operator) @vparfonov
• Implement automated "happy path" e2e test (step 1, 3 and 4) E2E tests suite for Che 7 #12728 @rhopp
• Use "happy path" e2e test as PR check on: che and che-theia Run E2E Happy path tests as PR check on che-theia repository #13326 @rhopp
• Update projects widget in Create New Workspace Panel Update projects widget in Create New Workspace Panel #13665 Fix selenium tests after last dashboard changes #13856 @ashumilova
• Remove Che CLI container images from build Remove docker cli from Che7 #13649 @benoitf
• Remove GWT @skabashnyuk @vparfonov
• Remove Che CLI container images eclipse/che:nightly and eclipse/che:latest from DockerHub (has been removed from source code) @vparfonov
• Deprecate and remove method /api/devfile/method Deprecate and remove /api/devfile method #13867 @skabashnyuk
• Give more flexibility on where devfile registry can served up Give more flexibility on where devfile registry can served up #13634
• Adapt "Stacks" in UD to Che 7 Adapt "Stacks" in UD to Che 7 #13811 @ashumilova
• Release script for che-operator Implement scripts to release che-operator #13780 @davidfestal
• Create a nightly image for che-theia image on branch 7.0.0 Provides a nightly image for che-theia image on branch 7.0.0 #13782 @evidolob

Docs

• The document draft should be shared on a google doc.
• Ping @l0rd, @slemeur and @rkratky once the article is ready for review (e.g. with a comment on the google doc).
• Review of the documents happens on the google doc
• Once the review is done the article will be published by the doc team to https://github.com/eclipse/che-docs/

Topics

• Running Che remotely
  • Installing Che on AWS, OpenShift 3, OpenShift 4 - @benoitf - PR #768
  • Installing Che on GCP - @benoitf - PR #770
  • Installing Che on Azure - @benoitf - PR #769
• Hosted Che - @ibuziuk - PR #729
• Che architecture @l0rd - PR #756
• Che-Theia IDE basics - @vparfonov - PR #763
• Making a workspace portable using a Devfile - @metlos - PR #752
• Converting a Che 6 Workspace to a Che 7 devfile - @olexii4 - PR #766
• Retrieving Che logs - @tsmaeder - PR #765
• Devfile and Plugin registries customization - @l0rd - PR #767
• Securing Che - @skabashnyuk - PR #758
• Creating a workspace from code sample - @nickboldt - PR #737
• Creating a workspace by importing source code of your project - @nickboldt - PR #737
• Importing a Kubernetes application into a Che workspace - @l0rd - PR #760
• Using a Visual Studio Code extension in Che - @mikola - PR #754
• Remotely accessing your workspace (open a shell) - @l0rd - PR #761
• List the supported k8s resources in a devfile (c.f. Create a list of OpenShift objects that we can/can't support in devfile or workspace recipe #12899) - @slemeur - PR #753

Other documentation related tasks

• Document known issue using github query @rkratky. Candidate issues:
  https://github.com/eclipse/che-operator/issues/31
  PKIX error and impossible to start workspaces on OCP 4.1 #13607
  bright fonts are not set on dark theme on Firefox #13442
• Update issues template:
  • for updating the content of bugs/questions/features Update github templates when submitting new issues #13648 @benoitf
  • main issues template like https://github.com/gatsbyjs/gatsby/issues/new/choose @slemeur
• Update wiki and readme files @slemeur @sunix

END 2 END TEST SUITE STATUS

Test suite description: #12728

STEP	IMPLEMENTED	STATUS	ISSUES
1. Deployment (operator)	YES	NEED WORKAROUNDS	che-incubator/chectl#92 https://github.com/che-incubator/chectl#145
3. Start a Workspace from a devfile	YES	NEED WORKAROUNDS	#13427 #11867 #13498
4. Use Java IDE features and the inner loop	PR: #13615	NOT TESTED

"Happy path" failures:

• Happy Path test is sometimes failing on "Error highlighting" step Happy Path test is sometimes failing on "Error highlighting" step #13865 @rhopp
• Happy Path test sometimes fail on "Validation of debug functionality" Happy Path test sometimes fail on "Validation of debug functionality" #13864 @rhopp

RELEASE ACCEPTANCE CRITERIA (manual tests)

N/A

MARKETING AND PROMOTION (Postponed to September 2019)

Tasks to complete a couple of weeks after the release:

• Update Eclipse Che website @slemeur
  • Getting started factories updates @ibuziuk After update of che.openshift.io to Che 7 GA all Che 6 sample from SaaS Cloud will stop working (need to replace with devfile equivalent) redhat-developer/rh-che#1451 / Update che.openshift.io to Che 7 GA / '7.1.0' version redhat-developer/rh-che#1490
• Blog post series of major Che 7 features (need a list) @slemeur
• Collect testimonials for Che 7 (user, OEM, plug-in developer) @slemeur
• Create sample tweets to use around Che 7 release for #chetips @jesse
• Prepare webinar to present Che 7 @slemeur @l0rd @gorkem

FAQ

What are the branches where the endgame issues/features will be merged? Master branch or a dedicated release branch?
Master branch. A communication has been sent to che-dev to inform that for a couple of sprints we won't accept any PR that is not considered a blocker. For that purpose the following engineers will be responsible to approve (or not) PRs on the following repositories:

• che server: @l0rd, @rhopp, @nickboldt
• devfile-registry: @l0rd, @rhopp, @skabashnyuk
• plugin-registry: @l0rd, @rhopp, @skabashnyuk
• che-theia: @l0rd, @rhopp, @evidolob
• che-operator: @l0rd, @rhopp, @davidfestal
• che-broker: @l0rd, @rhopp, @nickboldt
• chectl: @l0rd, @rhopp, @benoitf

Note that in any case PRs need to be reviewed by code owners as well (as usual)

How do we review new bugs and decide if they should be included to the endgame?
A list of curators will do the triage of new issues (blocker/no blocker).
Issues that are not considered as blockers won't be included in the endgame.
The curator will send a message to the mattermost Eclipse Che chat to inform the community about the triaging.
These are the curators:

• Monday: @l0rd
• Tuesday: @nickboldt
• Wednesday: @slemeur
• Thursday: @tsmaeder
• Friday: @rhopp

Issues that are not considered blockers but sev1 should be included in the 7.1 milestone

How do we protect against last minute changes in 3rd party dependency (e.g. theia)? Are we going to create a branch/tag before the release?
These are the tasks that we will take to use a stable version of Theia:

• Create a branch on theia repository (e.g. che-7.0.0) where we will cherry pick the commits that we want to include in Che @evidolob
• Create a branch on che-theia (e.g. 7.0.0) that should use theia branch mentioned above @evidolob
• Communicate to the Theia community @evidolob

Are we continuing to do RC releases or are we going to wait until we have the endgame completed?
We do releases as usual

[ibuziuk]

Can we remove Hide issues on non che repositories (without migrating issues) @tsmaeder @evidolob @ibuziuk since as I recall it was decided not to do this @slemeur @l0rd

[l0rd]

@ibuziuk done

[l0rd]

Che 7 has been released August 14 2019.