Release Che v7.3.2

Is your task related to a problem? Please describe.

We may need to release Che 7.3.2. This task is to track the list of fixes that should be added to the release:

• 7.3.1 version uses obsolete version of the plugin-broker (v0.22 instead of v0.24) · Issue #15099 · eclipse/che
  • PR - https://github.com/eclipse/che/pull/15178
• macnine-exec Add absent /tmp folder in the exec image to fix task SIGINT termination https://github.com/eclipse/che-machine-exec/pull/57
• Dashboard should use default icon for devfiles when actual icon is inaccessible · Issue #15089 · eclipse/che
  • Airgap improvements:
    • https://github.com/eclipse/che-plugin-registry/pull/294
    • https://github.com/eclipse/che-devfile-registry/pull/143
• Plugin installation fails from che-theia workspace · Issue #15006 · eclipse/che
• The token-exchange setup during Keycloak configuration fails on CRW #15152
• [CRW-466] Get plugins from theia-ide does not work if CRW 2.0 deployed with switched on TLS

Release status

• che-theia @evidolob eclipse/che-theia:7.3.2
• che-machine-exec @ibuziuk quay.io/eclipse/che-machine-exec:7.3.2 / https://quay.io/repository/eclipse/che-machine-exec?tab=tags&tag=7.3.2
  • https://github.com/eclipse/che-machine-exec/pull/58
• che-plugin-registry @ibuziuk quay.io/eclipse/che-plugin-registry:7.3.2 https://quay.io/repository/eclipse/che-plugin-registry?tab=tags&tag=7.3.2
  • https://github.com/eclipse/che-plugin-registry/pull/297
• che-devfile-registry @ibuziuk quay.io/eclipse/che-devfile-registry:7.3.2 https://quay.io/repository/eclipse/che-devfile-registry?tab=tags&tag=7.3.2
  • https://github.com/eclipse/che-devfile-registry/pull/145
• che @vparfonov
  • che-parent
  • che-docs
  • che
• che-operator @davidfestal
• chectl @benoitf

[ibuziuk]

@amisevsk I think we probably need to backport tthose PRs to 7.3.2

• https://github.com/eclipse/che-plugin-registry/pull/282
• https://github.com/eclipse/che-devfile-registry/pull/136

[l0rd]

@ibuziuk added

@vparfonov we want this to be included in CRW 2.0.0 so we should release at the beginning of next week. Something important to mention is that as far as I am concerned those are not blockers: if we don’t have a fix for them by the beginning of next week we can add them in the doc among “Known Issues”. In other words: let’s do the 7.3.2 release at latest next Tuesday with whatever we have. Does that make sense?