Today we have 4 tech preview containers, which don't get updated very often and which include several 3rd party lang servers.

• stacks-cpp
• stacks-golang
• stacks-dotnet (x64 only) ==> udi image, but not the udi-openj9 one
• stacks-php

To simplify the user experience and to make build process more efficient, we can collapse these into a single Universal Developer Image:

• udi-tech-preview

Once the new image is productized, we will have to update the devfiles and sync scripts to ensure that all the assets are built, published to GH releases, collected into pkgs.devel, and built in Brew.

If any of those languages are ready to be considered GA quality, we could consider moving them from the TP image to a GA one. See CRW-2463.

As of Nov 22, no desire from team leads, architecture, or support to promote anything from TP to GA.

But Mario would like to see the TP content in the GA container. If we want to achieve that, we need to implement labels or grouping in the dashboard, so that we can differentiate TP from GA (and as an added bonus, community from product). See https://github.com/eclipse/che/issues/19953 -> https://github.com/eclipse/che/issues/19633

With the above issue completed, we can now start moving content from the stacks-* images to:

• udi