From e46695a552137ef2c2f849cf4fa0c2f0f6cee900 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Br=C3=BCmmer?= Date: Mon, 4 Aug 2025 17:47:26 +0200 Subject: [PATCH 01/11] Add clarification on feature availability and infrastructure requirements --- doc/policy/development_stages_support.md | 29 ++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/doc/policy/development_stages_support.md b/doc/policy/development_stages_support.md index c9b015e6de54a6..f2a57c1a9b844d 100644 --- a/doc/policy/development_stages_support.md +++ b/doc/policy/development_stages_support.md @@ -76,3 +76,32 @@ Generally available features: - Are [fully supported](https://about.gitlab.com/support/statement-of-support/) and documented. - Have a complete user experience aligned with GitLab design standards. - Must be available on all GitLab platforms (GitLab.com, GitLab.com Cells, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government). + +## Feature availability and infrastructure requirements + +Feature **availability** and **accessibility** are distinct concepts: + +* Feature availability refers to a feature being production-ready, supported, and documented on a GitLab platform. The feature is available for adoption by customers, but may require additional configuration or infrastructure. +* Feature accessibility describes the characteristic that users can start using the feature without any additional infrastructure dependencies or configuration. + +In contrast to availability, feature accessability varies by GitLab platform: + +**GitLab SaaS platforms (GitLab.com, GitLab Dedicated):** GitLab provides and manages all infrastructure requirements for generally available features. All generally available features are both available and accessible to customers without additional infrastructure investment. + +**GitLab Self-Managed:** Customers are responsible for providing and managing all infrastructure requirements. Feature availability does not guarantee feature accessibility without additional infrastructure investment. Features may require customers to deploy and manage additional components and dependencies. + +Prominent examples for generally available but not accessible features include [GitLab CI](https://docs.gitlab.com/ci/), which requires a [GitLab Runner](https://docs.gitlab.com/runner/) deployment, [GitLab Pages](https://docs.gitlab.com/user/project/pages/) which requires [specific configuration](https://docs.gitlab.com/administration/pages/) and [Advanced Search](https://docs.gitlab.com/user/search/advanced_search/), which requires Elasticsearch or OpenSearch integration. + +For GitLab Self-Managed specifically, making features accessible to users may require: + +* Additional stateful components such as databases, search engines, or message queues +* Specific deployment models (e.g., Kubernetes-only features not available in the Omnibus package) +* Minimum resource requirements beyond standard GitLab recommendations +* External service dependencies or specialized infrastructure capabilities + +These definitions are in line with our self-managed packaging approach: + +* Core features and their dependencies are packaged for all supported deployment models. They are available and accessible on all GitLab instances. This includes the rails monolith and Gitaly. +* Some advanced features may require customers to deploy additional infrastructure components and configurations or use deployment models that can support their operational requirements. They will only be accessible to customers providing these requirements. + +Self-Managed customers should review feature documentation to understand specific infrastructure requirements, supported deployment models, and any additional components needed for feature adoption. Features requiring additional infrastructure will provide clear guidance on deployment options and graceful degradation behavior when dependencies are unavailable. -- GitLab From 2dc0492ff7634f44e4e86b1edb138850e69c81d0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Br=C3=BCmmer?= Date: Tue, 5 Aug 2025 13:18:24 +0200 Subject: [PATCH 02/11] Incorporate technical writing recommendations --- doc/policy/development_stages_support.md | 45 ++++++++++++++++-------- 1 file changed, 30 insertions(+), 15 deletions(-) diff --git a/doc/policy/development_stages_support.md b/doc/policy/development_stages_support.md index f2a57c1a9b844d..f658a8ec3f2349 100644 --- a/doc/policy/development_stages_support.md +++ b/doc/policy/development_stages_support.md @@ -77,31 +77,46 @@ Generally available features: - Have a complete user experience aligned with GitLab design standards. - Must be available on all GitLab platforms (GitLab.com, GitLab.com Cells, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government). -## Feature availability and infrastructure requirements +## Feature availability and accessibility Feature **availability** and **accessibility** are distinct concepts: -* Feature availability refers to a feature being production-ready, supported, and documented on a GitLab platform. The feature is available for adoption by customers, but may require additional configuration or infrastructure. -* Feature accessibility describes the characteristic that users can start using the feature without any additional infrastructure dependencies or configuration. +- An available feature is production-ready, supported, and documented on a GitLab platform. Available features can be adopted by customers, but might require additional + configuration or infrastructure. +- An accessible feature can be used without any additional infrastructure dependencies or configuration. -In contrast to availability, feature accessability varies by GitLab platform: +Unlike availability, feature accessibility varies by GitLab platform: -**GitLab SaaS platforms (GitLab.com, GitLab Dedicated):** GitLab provides and manages all infrastructure requirements for generally available features. All generally available features are both available and accessible to customers without additional infrastructure investment. +- GitLab SaaS platforms (GitLab.com, GitLab Dedicated): GitLab provides and manages all infrastructure requirements for generally available features. All generally available + features are both available and accessible to customers without additional infrastructure investment. +- GitLab Self-Managed: Customers are responsible for providing and managing all infrastructure requirements. Feature availability does not guarantee + feature accessibility without additional infrastructure investment. Features might require customers to deploy and manage additional components and dependencies. -**GitLab Self-Managed:** Customers are responsible for providing and managing all infrastructure requirements. Feature availability does not guarantee feature accessibility without additional infrastructure investment. Features may require customers to deploy and manage additional components and dependencies. +Prominent examples of features that are generally available but not accessible include: -Prominent examples for generally available but not accessible features include [GitLab CI](https://docs.gitlab.com/ci/), which requires a [GitLab Runner](https://docs.gitlab.com/runner/) deployment, [GitLab Pages](https://docs.gitlab.com/user/project/pages/) which requires [specific configuration](https://docs.gitlab.com/administration/pages/) and [Advanced Search](https://docs.gitlab.com/user/search/advanced_search/), which requires Elasticsearch or OpenSearch integration. +- [GitLab CI/CD](../ci/_index.md), which requires a [GitLab Runner](https://docs.gitlab.com/runner/) deployment. +- [GitLab Pages](../user/project/pages/_index.md), which requires [specific configuration](../administration/pages/_index.md). +- [Advanced Search](..//user/search/advanced_search.md), which requires Elasticsearch or OpenSearch integration. For GitLab Self-Managed specifically, making features accessible to users may require: -* Additional stateful components such as databases, search engines, or message queues -* Specific deployment models (e.g., Kubernetes-only features not available in the Omnibus package) -* Minimum resource requirements beyond standard GitLab recommendations -* External service dependencies or specialized infrastructure capabilities +- Additional stateful components such as databases, search engines, or message queues. +- Specific deployment models. For example, Kubernetes-only features that are not available in the Linux package. +- Minimum resource requirements beyond standard GitLab recommendations. +- External service dependencies or specialized infrastructure capabilities. -These definitions are in line with our self-managed packaging approach: +These definitions are in line with our GitLab Self-Managed packaging approach: -* Core features and their dependencies are packaged for all supported deployment models. They are available and accessible on all GitLab instances. This includes the rails monolith and Gitaly. -* Some advanced features may require customers to deploy additional infrastructure components and configurations or use deployment models that can support their operational requirements. They will only be accessible to customers providing these requirements. +- Core features and their dependencies are packaged for all supported deployment models. They are available and accessible on all GitLab instances. This + includes GitLab itself and Gitaly. +- Some advanced features might require customers to deploy additional infrastructure components and configurations or use deployment models that can + support their operational requirements. They are only accessible to customers providing these requirements. -Self-Managed customers should review feature documentation to understand specific infrastructure requirements, supported deployment models, and any additional components needed for feature adoption. Features requiring additional infrastructure will provide clear guidance on deployment options and graceful degradation behavior when dependencies are unavailable. +GitLab Self-Managed customers should review feature documentation to understand: + +- Specific infrastructure requirements. +- Supported deployment models. +- Any additional components needed for feature adoption. + +Features requiring additional infrastructure will provide clear guidance on deployment options and graceful degradation behavior when dependencies +are unavailable. -- GitLab From fe20fe32dd970de0e64f421184350afcb175276c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Br=C3=BCmmer?= Date: Tue, 5 Aug 2025 13:50:42 +0200 Subject: [PATCH 03/11] Change accessibility to adoptability out-of-the-box --- doc/policy/development_stages_support.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/doc/policy/development_stages_support.md b/doc/policy/development_stages_support.md index f658a8ec3f2349..0b191593fef87e 100644 --- a/doc/policy/development_stages_support.md +++ b/doc/policy/development_stages_support.md @@ -77,28 +77,28 @@ Generally available features: - Have a complete user experience aligned with GitLab design standards. - Must be available on all GitLab platforms (GitLab.com, GitLab.com Cells, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government). -## Feature availability and accessibility +## Feature availability and adoptability out-of-the-box -Feature **availability** and **accessibility** are distinct concepts: +Feature **availability** and **adoptability** out-of-the-box are distinct concepts: -- An available feature is production-ready, supported, and documented on a GitLab platform. Available features can be adopted by customers, but might require additional +- An available feature is production-ready, supported, and documented on all GitLab platforms. Available features can be adopted by customers, but might require additional configuration or infrastructure. -- An accessible feature can be used without any additional infrastructure dependencies or configuration. +- An out-of-the-box adoptable feature can be used without any additional infrastructure dependencies or configuration. -Unlike availability, feature accessibility varies by GitLab platform: +Out-of-the-box adoptability varies by GitLab platform, while availability does not: - GitLab SaaS platforms (GitLab.com, GitLab Dedicated): GitLab provides and manages all infrastructure requirements for generally available features. All generally available - features are both available and accessible to customers without additional infrastructure investment. + features are both available and adoptable out-of-the-box by customers. - GitLab Self-Managed: Customers are responsible for providing and managing all infrastructure requirements. Feature availability does not guarantee - feature accessibility without additional infrastructure investment. Features might require customers to deploy and manage additional components and dependencies. + out-of-the-box adoptability. Features might require customers to deploy and manage additional components and dependencies. -Prominent examples of features that are generally available but not accessible include: +Prominent examples of features that are generally available but not adoptable out-of-the-box include: - [GitLab CI/CD](../ci/_index.md), which requires a [GitLab Runner](https://docs.gitlab.com/runner/) deployment. - [GitLab Pages](../user/project/pages/_index.md), which requires [specific configuration](../administration/pages/_index.md). - [Advanced Search](..//user/search/advanced_search.md), which requires Elasticsearch or OpenSearch integration. -For GitLab Self-Managed specifically, making features accessible to users may require: +For GitLab Self-Managed specifically, making features adoptable to users may require: - Additional stateful components such as databases, search engines, or message queues. - Specific deployment models. For example, Kubernetes-only features that are not available in the Linux package. @@ -107,10 +107,10 @@ For GitLab Self-Managed specifically, making features accessible to users may re These definitions are in line with our GitLab Self-Managed packaging approach: -- Core features and their dependencies are packaged for all supported deployment models. They are available and accessible on all GitLab instances. This +- Foundational features and their dependencies are packaged for all supported deployment models. They are available and adoptable out-of-the-box on all GitLab instances. This includes GitLab itself and Gitaly. - Some advanced features might require customers to deploy additional infrastructure components and configurations or use deployment models that can - support their operational requirements. They are only accessible to customers providing these requirements. + support their operational requirements. They are only adoptable by customers providing these requirements. GitLab Self-Managed customers should review feature documentation to understand: -- GitLab From b14a1472ef3918850f1b5fa6d8c0df7781433f10 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Br=C3=BCmmer?= Date: Tue, 5 Aug 2025 13:56:05 +0200 Subject: [PATCH 04/11] Minor language improvements --- doc/policy/development_stages_support.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/policy/development_stages_support.md b/doc/policy/development_stages_support.md index 0b191593fef87e..1b76cfce65e5c1 100644 --- a/doc/policy/development_stages_support.md +++ b/doc/policy/development_stages_support.md @@ -109,8 +109,8 @@ These definitions are in line with our GitLab Self-Managed packaging approach: - Foundational features and their dependencies are packaged for all supported deployment models. They are available and adoptable out-of-the-box on all GitLab instances. This includes GitLab itself and Gitaly. -- Some advanced features might require customers to deploy additional infrastructure components and configurations or use deployment models that can - support their operational requirements. They are only adoptable by customers providing these requirements. +- Some advanced features might require customers to deploy additional infrastructure components and configurations, or use deployment models that can + support their operational requirements. They are only adoptable by customers providing for these requirements. GitLab Self-Managed customers should review feature documentation to understand: -- GitLab From 749d37944896c049bbd6a42480c1bcdabf978ba1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Br=C3=BCmmer?= Date: Wed, 6 Aug 2025 11:03:16 +0200 Subject: [PATCH 05/11] Fix double slash in docs link --- doc/policy/development_stages_support.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/policy/development_stages_support.md b/doc/policy/development_stages_support.md index 1b76cfce65e5c1..083d9aa6951f50 100644 --- a/doc/policy/development_stages_support.md +++ b/doc/policy/development_stages_support.md @@ -96,7 +96,7 @@ Prominent examples of features that are generally available but not adoptable ou - [GitLab CI/CD](../ci/_index.md), which requires a [GitLab Runner](https://docs.gitlab.com/runner/) deployment. - [GitLab Pages](../user/project/pages/_index.md), which requires [specific configuration](../administration/pages/_index.md). -- [Advanced Search](..//user/search/advanced_search.md), which requires Elasticsearch or OpenSearch integration. +- [Advanced Search](../user/search/advanced_search.md), which requires Elasticsearch or OpenSearch integration. For GitLab Self-Managed specifically, making features adoptable to users may require: -- GitLab From bcc52a06e7405c97744cd4324178f14e1ed9f880 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Br=C3=BCmmer?= Date: Wed, 13 Aug 2025 13:52:20 +0200 Subject: [PATCH 06/11] Link self managed segmentation --- doc/policy/development_stages_support.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/policy/development_stages_support.md b/doc/policy/development_stages_support.md index 083d9aa6951f50..ab4eeab149b7bf 100644 --- a/doc/policy/development_stages_support.md +++ b/doc/policy/development_stages_support.md @@ -105,7 +105,7 @@ For GitLab Self-Managed specifically, making features adoptable to users may req - Minimum resource requirements beyond standard GitLab recommendations. - External service dependencies or specialized infrastructure capabilities. -These definitions are in line with our GitLab Self-Managed packaging approach: +These definitions are in line with our [GitLab Self-Managed packaging approach](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/selfmanaged_segmentation/): - Foundational features and their dependencies are packaged for all supported deployment models. They are available and adoptable out-of-the-box on all GitLab instances. This includes GitLab itself and Gitaly. -- GitLab From 2f48843de544abe5cfc208eedecc599bec4a6f88 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Br=C3=BCmmer?= Date: Wed, 13 Aug 2025 15:46:56 +0200 Subject: [PATCH 07/11] Specify self-managed in out of the box adoptability restrictions --- doc/policy/development_stages_support.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/policy/development_stages_support.md b/doc/policy/development_stages_support.md index ab4eeab149b7bf..4729dbfbf0eb6b 100644 --- a/doc/policy/development_stages_support.md +++ b/doc/policy/development_stages_support.md @@ -92,7 +92,7 @@ Out-of-the-box adoptability varies by GitLab platform, while availability does n - GitLab Self-Managed: Customers are responsible for providing and managing all infrastructure requirements. Feature availability does not guarantee out-of-the-box adoptability. Features might require customers to deploy and manage additional components and dependencies. -Prominent examples of features that are generally available but not adoptable out-of-the-box include: +Prominent examples of features that are generally available but not adoptable out-of-the-box on GitLab Self-Managed include: - [GitLab CI/CD](../ci/_index.md), which requires a [GitLab Runner](https://docs.gitlab.com/runner/) deployment. - [GitLab Pages](../user/project/pages/_index.md), which requires [specific configuration](../administration/pages/_index.md). -- GitLab From 437bd6f38788d96e5d061cb89c4c59de24f3da9e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Br=C3=BCmmer?= Date: Fri, 15 Aug 2025 17:26:53 +0200 Subject: [PATCH 08/11] Apply technical writer review suggestions --- doc/policy/development_stages_support.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/policy/development_stages_support.md b/doc/policy/development_stages_support.md index 4729dbfbf0eb6b..01790f2be9ca49 100644 --- a/doc/policy/development_stages_support.md +++ b/doc/policy/development_stages_support.md @@ -77,20 +77,20 @@ Generally available features: - Have a complete user experience aligned with GitLab design standards. - Must be available on all GitLab platforms (GitLab.com, GitLab.com Cells, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government). -## Feature availability and adoptability out-of-the-box +## Feature availability and adoptability -Feature **availability** and **adoptability** out-of-the-box are distinct concepts: +The **availability** and **adoptability** of features out-of-the-box are distinct: - An available feature is production-ready, supported, and documented on all GitLab platforms. Available features can be adopted by customers, but might require additional configuration or infrastructure. -- An out-of-the-box adoptable feature can be used without any additional infrastructure dependencies or configuration. +- A feature that is adoptable out-of-the-box can be used without any additional infrastructure dependencies or configuration. -Out-of-the-box adoptability varies by GitLab platform, while availability does not: +Adoptability of features out-of-the-box varies by GitLab platform, while availability of features does not: - GitLab SaaS platforms (GitLab.com, GitLab Dedicated): GitLab provides and manages all infrastructure requirements for generally available features. All generally available features are both available and adoptable out-of-the-box by customers. - GitLab Self-Managed: Customers are responsible for providing and managing all infrastructure requirements. Feature availability does not guarantee - out-of-the-box adoptability. Features might require customers to deploy and manage additional components and dependencies. + that a feature is adoptable out-of-the-box. Features might require customers to deploy and manage additional components and dependencies. Prominent examples of features that are generally available but not adoptable out-of-the-box on GitLab Self-Managed include: @@ -98,7 +98,7 @@ Prominent examples of features that are generally available but not adoptable ou - [GitLab Pages](../user/project/pages/_index.md), which requires [specific configuration](../administration/pages/_index.md). - [Advanced Search](../user/search/advanced_search.md), which requires Elasticsearch or OpenSearch integration. -For GitLab Self-Managed specifically, making features adoptable to users may require: +For GitLab Self-Managed specifically, making features adoptable to users might require: - Additional stateful components such as databases, search engines, or message queues. - Specific deployment models. For example, Kubernetes-only features that are not available in the Linux package. @@ -118,5 +118,5 @@ GitLab Self-Managed customers should review feature documentation to understand: - Supported deployment models. - Any additional components needed for feature adoption. -Features requiring additional infrastructure will provide clear guidance on deployment options and graceful degradation behavior when dependencies +Documentation for features that require additional infrastructure provide clear guidance on deployment options and graceful degradation behavior when dependencies are unavailable. -- GitLab From 2e1383dc1e2095e6fac07917b45a6fc0164df497 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Br=C3=BCmmer?= Date: Fri, 5 Sep 2025 18:02:13 +0200 Subject: [PATCH 09/11] remove out-of-the-box terminology and replace with infrastructure requirements --- doc/policy/development_stages_support.md | 25 ++++++++++-------------- 1 file changed, 10 insertions(+), 15 deletions(-) diff --git a/doc/policy/development_stages_support.md b/doc/policy/development_stages_support.md index 01790f2be9ca49..18f3e0cff98a66 100644 --- a/doc/policy/development_stages_support.md +++ b/doc/policy/development_stages_support.md @@ -77,28 +77,24 @@ Generally available features: - Have a complete user experience aligned with GitLab design standards. - Must be available on all GitLab platforms (GitLab.com, GitLab.com Cells, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government). -## Feature availability and adoptability +## Feature availability and infrastructure requirements -The **availability** and **adoptability** of features out-of-the-box are distinct: +An available feature is production-ready, supported, and documented on all GitLab platforms. +We aim to make features as easy to adopt as possible. However, some features may require additional infrastructure components, specific deployment models, or configuration to function. -- An available feature is production-ready, supported, and documented on all GitLab platforms. Available features can be adopted by customers, but might require additional - configuration or infrastructure. -- A feature that is adoptable out-of-the-box can be used without any additional infrastructure dependencies or configuration. - -Adoptability of features out-of-the-box varies by GitLab platform, while availability of features does not: +Infrastructure requirements vary by GitLab platform: - GitLab SaaS platforms (GitLab.com, GitLab Dedicated): GitLab provides and manages all infrastructure requirements for generally available features. All generally available - features are both available and adoptable out-of-the-box by customers. -- GitLab Self-Managed: Customers are responsible for providing and managing all infrastructure requirements. Feature availability does not guarantee - that a feature is adoptable out-of-the-box. Features might require customers to deploy and manage additional components and dependencies. + features can be adopted without additional customer infrastructure investment. +- GitLab Self-Managed: Customers are responsible for providing and managing all infrastructure requirements. Feature availability does not guarantee that features can be adopted without additional infrastructure or configuration. -Prominent examples of features that are generally available but not adoptable out-of-the-box on GitLab Self-Managed include: +Prominent examples of features that are generally available but may require additional infrastructure on GitLab Self-Managed include: - [GitLab CI/CD](../ci/_index.md), which requires a [GitLab Runner](https://docs.gitlab.com/runner/) deployment. - [GitLab Pages](../user/project/pages/_index.md), which requires [specific configuration](../administration/pages/_index.md). - [Advanced Search](../user/search/advanced_search.md), which requires Elasticsearch or OpenSearch integration. -For GitLab Self-Managed specifically, making features adoptable to users might require: +For GitLab Self-Managed specifically, adopting features might require: - Additional stateful components such as databases, search engines, or message queues. - Specific deployment models. For example, Kubernetes-only features that are not available in the Linux package. @@ -107,10 +103,9 @@ For GitLab Self-Managed specifically, making features adoptable to users might r These definitions are in line with our [GitLab Self-Managed packaging approach](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/selfmanaged_segmentation/): -- Foundational features and their dependencies are packaged for all supported deployment models. They are available and adoptable out-of-the-box on all GitLab instances. This - includes GitLab itself and Gitaly. +- Foundational features and their dependencies are packaged for all supported deployment models. They are available and can be adopted on all GitLab instances without additional infrastructure. This includes GitLab itself and Gitaly. - Some advanced features might require customers to deploy additional infrastructure components and configurations, or use deployment models that can - support their operational requirements. They are only adoptable by customers providing for these requirements. + support their operational requirements. They can only be adopted by customers who provide these requirements. GitLab Self-Managed customers should review feature documentation to understand: -- GitLab From 11aeaba1da634ef53d35964aad879e60d1f7763d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Br=C3=BCmmer?= Date: Tue, 9 Sep 2025 15:01:00 +0200 Subject: [PATCH 10/11] Further adjustments to text flow and content --- doc/policy/development_stages_support.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/doc/policy/development_stages_support.md b/doc/policy/development_stages_support.md index 18f3e0cff98a66..ec0d277a71afba 100644 --- a/doc/policy/development_stages_support.md +++ b/doc/policy/development_stages_support.md @@ -79,21 +79,20 @@ Generally available features: ## Feature availability and infrastructure requirements -An available feature is production-ready, supported, and documented on all GitLab platforms. +A gemerally available feature is production-ready, supported, and documented on all GitLab platforms. We aim to make features as easy to adopt as possible. However, some features may require additional infrastructure components, specific deployment models, or configuration to function. -Infrastructure requirements vary by GitLab platform: - -- GitLab SaaS platforms (GitLab.com, GitLab Dedicated): GitLab provides and manages all infrastructure requirements for generally available features. All generally available - features can be adopted without additional customer infrastructure investment. -- GitLab Self-Managed: Customers are responsible for providing and managing all infrastructure requirements. Feature availability does not guarantee that features can be adopted without additional infrastructure or configuration. - -Prominent examples of features that are generally available but may require additional infrastructure on GitLab Self-Managed include: +Prominent examples of features that are generally available but may require additional infrastructure include: - [GitLab CI/CD](../ci/_index.md), which requires a [GitLab Runner](https://docs.gitlab.com/runner/) deployment. - [GitLab Pages](../user/project/pages/_index.md), which requires [specific configuration](../administration/pages/_index.md). - [Advanced Search](../user/search/advanced_search.md), which requires Elasticsearch or OpenSearch integration. +These infrastructure requirements vary by GitLab platform: + +- GitLab SaaS platforms (GitLab.com, GitLab Dedicated): Feature the lowest total cost of ownership, because no infrastructure management is required. GitLab provides and manages all infrastructure requirements for generally available features, so they can be adopted without additional customer infrastructure investment. +- GitLab Self-Managed: Features complete control for customers over infrastructure and data. Customers are responsible for providing and managing all infrastructure requirements. Feature availability does not guarantee that features can be adopted without additional infrastructure or configuration. + For GitLab Self-Managed specifically, adopting features might require: - Additional stateful components such as databases, search engines, or message queues. -- GitLab From f73551ba86750a93616ae1c8f85889dfd9d19406 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Br=C3=BCmmer?= Date: Tue, 9 Sep 2025 15:03:00 +0200 Subject: [PATCH 11/11] Fix typo --- doc/policy/development_stages_support.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/policy/development_stages_support.md b/doc/policy/development_stages_support.md index ec0d277a71afba..2d4d7b70ea5cd8 100644 --- a/doc/policy/development_stages_support.md +++ b/doc/policy/development_stages_support.md @@ -79,7 +79,7 @@ Generally available features: ## Feature availability and infrastructure requirements -A gemerally available feature is production-ready, supported, and documented on all GitLab platforms. +A generally available feature is production-ready, supported, and documented on all GitLab platforms. We aim to make features as easy to adopt as possible. However, some features may require additional infrastructure components, specific deployment models, or configuration to function. Prominent examples of features that are generally available but may require additional infrastructure include: -- GitLab