You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment we have no defined set of platforms we support/test for with Gitpod Self-Hosted. We must produce a defined set of platforms we support, maintain this set and subsequently test those platforms. As a first step, we should produce this list and add it to the documentation.
The Platform Support Matrix would be structured along the following dimensions:
We could also add another column to indicate something of a support/test level. I.e. there are probably many more combinations we expect to work but don't explicitly test. Also, we'll want to deprecate combinations in the future and should be able to mark them as deprecated.
The text was updated successfully, but these errors were encountered:
We might want to split this up even for specific features. In general we're following a strategy best summed up as "common features with common requirements; specialised features can use specialised requirements".
For example:
common feature, common requirements: when user-namespaced workspaces become the default, this feature must not impose specialised requirements anymore (e.g. Ubuntu as OS)
specialised feature, specialised requirement: dynamic resource limiting done by ws-daemon requires containerd in a particular version.
On top of the matrix described above, we should explicitly list what we consider specialised features, and what requirements they impose.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Uh oh!
There was an error while loading. Please reload this page.
At the moment we have no defined set of platforms we support/test for with Gitpod Self-Hosted. We must produce a defined set of platforms we support, maintain this set and subsequently test those platforms. As a first step, we should produce this list and add it to the documentation.
The Platform Support Matrix would be structured along the following dimensions:
For example:
We could also add another column to indicate something of a support/test level. I.e. there are probably many more combinations we expect to work but don't explicitly test. Also, we'll want to deprecate combinations in the future and should be able to mark them as deprecated.
The text was updated successfully, but these errors were encountered: