Ilya Buziuk

probably we should consider using ` quay.io/devfile/universal-developer-image` instead of custom `quay.io/eclipse/che-docs:latest` for the tools container

> Could not overdraw the limit on dog-fooding with che-code editor: On dogfooding we do apply neither limits nor quotas, it should be verified on the Developer Sandbox staging enviroment

from the architectural point of view, I would like to avoid adding more complexity to the dashboard and making it the "glue" / pre-processing component without which some of the...

@elsony all the 3.x instances are affected, would it be possible to setup redirect from https://devfile.io/docs/devfile/2.2.0/user-guide/migrating-to-devfile-v2/ to https://devfile.io/docs/2.2.0-alpha/migrating-to-devfile-v2 ?

PR for fixing link on the dashboard end https://github.com/eclipse-che/che-dashboard/pull/611 (should be also backported to 7.52.x)

PRs have been merged including the backport to 7.52.x (Dev Spaces 3.2) - https://github.com/eclipse-che/che-dashboard/pull/613 @elsony could you please set up redirect for https://devfile.io/docs/devfile/2.2.0/user-guide/migrating-to-devfile-v2/ ?

thank you. Closing

Today, after merging all the relevant PRs and testing on dogfooding 2 more issues have been created that need to be resolved before closing this story: - https://github.com/eclipse/che/issues/21707 - https://github.com/eclipse/che/issues/21710

@ScrewTSW closing feel free to reopen

@AObuchow I would probably split the removal of the properties to a couple of PRs by domain similar to what has been done for storage related properties - https://github.com/eclipse-che/che-server/pull/330 `che.workspace.*`...