Release Che 7.27.1

List of pending issues / PRs

PRs related to DevWorkspace Integration - STEP1 Milestone:

• Include che.devworkspaces.enabled property by xbaran4
• Add in CRUD actions for the devworkspace in dashboard
• Che operator should be able to install DevWorkspace operator
• Che Operator should be able to install the Devworkspace che operator
• Make routing attributes allign with devfile attributes
• Increase resource limits for controller to avoid OOMKilled https://github.com/devfile/devworkspace-operator/pull/312
• Dashboard is not handling anymore ‘restart-workspace’ event https://github.com/eclipse/che/issues/19174

PRs related to release process improvements:

• generate changelog as part of che GH release https://github.com/eclipse/che/pull/19222
  • followup fix in https://github.com/eclipse/che/pull/19267
• https://github.com/eclipse/che-release/pull/30 (should be changed to call the action in eclipse/che repo, as it doesn’t work in che-release repo)
• https://github.com/che-incubator/devworkspace-che-operator/pull/23 DevWorkspace Che Operator release workflow
• Mattermost notifications (8 artifacts to release): https://github.com/eclipse/che/issues/18906#issuecomment-796472177

Release status

In series, the following will be released via che-release:

• che-theia, che-machine-exec, che-devfile registry,
• che-plugin-registry (once che-theia and machine-exec are done)
• che-parent, che-dashboard, che-workspace-loader, and che (server assembly)
  • Note that release to Maven Central is deprecated
• che-operator

Then, these steps will be done, which still require some manual intervention (PR verification is not yet automated):

• generation of OperatorHub PRs
• chectl

• che-theia, che-machine-exec, che-devfile-registry, che-plugin-registry
• che-parent, che-dashboard, che-workspace-loader, che
• che-operator (depends on all of the above)
• chectl (depends on che-operator)
• Che community operator PRs (depends on che-operator)
• che-docs PR (depends on che-operator)

If this is a .0 release:

• send reminder to TLs to triage unresolved issues
• complete current milestone
  • move incomplete deferred issues to backlog
  • move incomplete WIP issues to next milestone
  • close completed issues
  • close milestone

Process [1]	Script	Action	Container(s) + Artifact(s)
che-release	cico_release.sh	Action	n/a
che-theia	make-release.sh	Action	eclipse/che-theia
che-machine-exec	make-release.sh	Action	eclipse/che-machine-exec
che-devfile-registry	make-release.sh	Action	eclipse/che-devfile-registry
che-plugin-registry	make-release.sh	Action	eclipse/che-plugin-registry
che-parent	make-release.sh	Action	che-server [2]
che-dashboard	make-release.sh	Action	che-dashboard
che-workspace-loader	make-release.sh	Action	che-workspace-loader
che	make-release.sh	Action	che.core [2], eclipse/che-server, eclipse/che-endpoint-watcher, eclipse/che-keycloak, eclipse/che-postgres, eclipse/che-server, eclipse/che-e2e
che-operator	make-release.sh	Action	eclipse/che-operator
chectl	make-release.sh	Action	chectl releases

^[1] Overall process owner: @mkuznyetsov

^[2] Note that release of artifacts to Maven Central is deprecated and will be removed in the future.

[mkuznyetsov]

Had various issues related to plugin registries build and DWO release processes, which took until friday to be resolved

Now, che operator has been released and merged, altough just noticed that this file wasn’t updated, so investigating the reason why this happened: https://github.com/eclipse/che-operator/blob/master/deploy/olm-catalog/stable/eclipse-che-preview-openshift/manifests/che-operator.clusterserviceversion.yaml#L85 after this, the release of chectl, che-docs and community operator PRs will follow

[mkuznyetsov]

upd. release is done on our side, waiting for community-operator/docs PR to be merged