-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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.12.0 release #16690
Comments
Followup work from today's automation/release exercise is in #16732 |
Che server pieces are not yet done -- misunderstood @mkuznyetsov 's comments in slack. So... @tolusha since your operator and chectl steps are not fully ready to be hands-free, you can push them after he confirms Che server pieces are done. Or we can wait until after tomorrow's discussion re: how to improve the scripts/automation for consumption inside cico_release.sh script. |
Che server bits have been pushed to Quay & Nexus, so release may resume |
|
che-operator update was successfully tested on minikube and OpenShift 4.3 |
When testing 7.12.0 on a Hosted Che, we found those issues:
What we tested - all default devfiles in ephemeral mode (workspace startup, predefined commands running, basic LS support), workspace idling. |
community operators PR merged |
Next issues have been found during the testing on minikube:
|
See followup releases:
|
List of pending issues / PRs
Release status
In parallel, the following releases can be done:
Then in series:
eclipse/che-theia
eclipse/che-machine-exec
eclipse/che-plugin-registry
eclipse/che-devfile-registry
che.depmgt
eclipse/che-server
,eclipse/che-endpoint-watcher
,eclipse/che-keycloak
,eclipse/che-postgres
,eclipse/che-dev
,eclipse/che-server
,eclipse/che-dashboard-dev
,eclipse/che-e2e
eclipse/che-operator
The text was updated successfully, but these errors were encountered: