Merge pull request #1195 from run-ai/deprecation-extended-notice-219

Merge pull request #1194 from run-ai/deprecation-extended-notice

docs/home/whats-new-2-16.md

@@ -97,4 +97,6 @@ The following list of API endpoints and fields that have completed their depreca
 | /v1/k8s/clusters | The endpoint was removed and is replaced by /api/v1/clusters |
 | /v1/k8s/clusters/{uuid} | The endpoint was removed and is replaced by /api/v1/clusters/{uuid} |
 
+Run:ai does not recommend using API endpoints and fields marked as deprecated and will not add functionality to them. Once an API endpoint or field is marked as deprecated, Run:ai will stop supporting it after 2 major releases for self-hosted deployments, and after 6 months for SaaS deployments.
+
 For a full explanation of the API Deprecation policy, see the [Run:ai API Policy](../developer/admin-rest-api/overview.md#api-lifecycle-and-deprecation)

docs/home/whats-new-2-17.md

@@ -229,6 +229,8 @@ The following metrics are deprecated and replaced by API endpoints. For details
 | runai\_active\_job\_memory\_limits |
 | runai\_job\_memory\_used\_bytes |
 
+Run:ai does not recommend using API endpoints and fields marked as deprecated and will not add functionality to them. Once an API endpoint or field is marked as deprecated, Run:ai will stop supporting it after 2 major releases for self-hosted deployments, and after 6 months for SaaS deployments.
+
 For a full explanation of the API Deprecation policy, see the [Run:ai API Policy](../developer/admin-rest-api/overview.md#api-lifecycle-and-deprecation)
 
 

docs/home/whats-new-2-18.md

@@ -150,6 +150,7 @@ Run:ai REST API now supports job submission. The older, [Cluster API](../develop
 | /v1/k8s/clusters/{clusterId}/projects/{id} | /api/v1/org-unit/projects/{projectId} |
 | /v1/k8s/clusters/{clusterId}/projects/{id} | /api/v1/org-unit/projects/{projectId} + /api/v1/org-unit/projects/{projectId}/resources |
 
+Run:ai does not recommend using API endpoints and fields marked as deprecated and will not add functionality to them. Once an API endpoint or field is marked as deprecated, Run:ai will stop supporting it after 2 major releases for self-hosted deployments, and after 6 months for SaaS deployments.
 
 For a full explanation of the API Deprecation policy, see the [Run:ai API Policy](../developer/admin-rest-api/overview.md#api-lifecycle-and-deprecation)
 

docs/home/whats-new-2-19.md

@@ -305,6 +305,8 @@ The legacy navigation will be fully deprecated in the Q1/25 release, and during
 | /api/v1/workloads/distributed/spec/compute/migProfile ||
 | /api/v1/workloads/distributed/masterSpec/compute/migProfile ||
 
+Run:ai does not recommend using API endpoints and fields marked as deprecated and will not add functionality to them. Once an API endpoint or field is marked as deprecated, Run:ai will stop supporting it after 2 major releases for self-hosted deployments, and after 6 months for SaaS deployments.
+
 For a full explanation of the API Deprecation policy, see the [Run:ai API Policy](../developer/admin-rest-api/overview.md#api-lifecycle-and-deprecation)