added notes on deprecation policy #288

mahjongmen · 2024-12-09T14:05:08Z

This PR introduces a new section, 'Model Status', to the 'fern/pages/going-to-production/deprecations.mdx' file. This section provides a comprehensive overview of publicly released models, including their names, types, guaranteed availability, current status, deprecation, and shutdown information.

Changes:

A new section, 'Model Status', is added to the file, presenting a table with detailed information about publicly released models.
The table includes columns for 'Model Name', 'Type of Model', 'Guaranteed Available Until', 'Current Status', 'Deprecated', and 'Shutdown'.
The 'Model Name' column lists various models, such as 'command-r-plus-08-2024', 'command-r-08-2024', 'c4ai-aya-expanse-8b', and more.
The 'Type of Model' column categorizes models as 'Generative', 'Embeddings', or 'Rerankers'.
The 'Guaranteed Available Until' column specifies the date until which the models are guaranteed to be available.
The 'Current Status' column indicates the current status of the models, such as 'Active' or 'Legacy'.
The 'Deprecated' and 'Shutdown' columns provide information about the deprecation and shutdown status of the models, respectively.

github-actions · 2024-12-09T14:08:16Z

🌿 Preview your docs: https://cohere-preview-a821aa0b-e673-4065-8bc0-a4dcd1be5d97.docs.buildwithfern.com

manoj-cohere · 2024-12-16T19:39:29Z

fern/pages/going-to-production/deprecations.mdx

@@ -9,7 +9,7 @@ keywords: 'Cohere API, large language models, generative AI'
 createdAt: 'Wed Nov 27 2024 00:00:00 GMT+0000 (Coordinated Universal Time)'
 updatedAt: 'Wed Nov 27 2024 00:00:00 GMT+0000 (Coordinated Universal Time)'
 ---
-Find information around deprecated endpoints and models with their recommended replacements. 
+Find information around deprecated endpoints and models with their recommended replacements. All deprecation announcements applies to models being accessed through our API. It does not apply to models served/hosted/deployed outside our API, where ad-hoc deprecation policies apply.


Any reason to differentiate Platform vs API. It can be maintenance heavy. Why not simple one rule for all access mediums and channels ?

Just my food for thought, but Sagemaker costs us almost nothing to maintain and we are bounded by different deprecation patterns for different platforms (Azure vs. AWS vs. Oracle). If that is the case, we have full control over platform which allows us to have a clear deprecation policy here?

LMK if that doesn't make sense - both anthropic and OAI list their deprecations are for their API only.

Anthropic

Open AI

manoj-cohere · 2024-12-16T19:40:24Z

fern/pages/going-to-production/deprecations.mdx

 Once a model is deprecated, it is imperative to migrate all usage to a suitable replacement before the shutdown date. Requests to models and endpoints past the shutdown date will fail. 
 To ensure a smooth transition, we recommend thorough testing of your applications with the new models well before the shutdown date. If your team requires assistance, do not hesitate to reach out to [email protected].

+## Notifications
+Cohere notifies customer with active usage of models for upcoming shutdown dates. We notify customers of upcoming shutdown dates as follows: 


you mean warn users about the deprecated models?

yep adjusted

manoj-cohere · 2024-12-16T19:43:01Z

fern/pages/going-to-production/deprecations.mdx

+Cohere notifies customer with active usage of models for upcoming shutdown dates. We notify customers of upcoming shutdown dates as follows: 
+
+1. At model launch, we designate a “Guaranteed Available Until” date (at least one year out) 
+2. We provide at least 6 months(1) notice before model retirement for publicly release models


Why do we need (1) ? Isn't (2) sufficient so that based on usage we can take a call to whether to support or not.
See for example, Rerank Nimble and Rerank Express. They aren't on platform and we released for channels and we are forced to support it for 1yr even when there aren't much usages?

I see noted and changed

manoj-cohere · 2024-12-16T19:43:58Z

fern/pages/going-to-production/deprecations.mdx

+## Model Status
+All publicly released models are listed below with their status:
+
+| Model Name                                  | Type of Model | Guaranteed Available Until | Current Status | Deprecated | Shutdown |


this list can go stale very often. Is this going to be the Single place for all our public models and policies?

We have this list: https://docs.cohere.com/docs/models but this list shows the models and where they are available.

I like the idea of having separate lists where this is just focused on deprecation. We do need to be on top of this list though as well as the other list

co-sudip · 2024-12-17T05:30:17Z

fern/pages/going-to-production/deprecations.mdx

@@ -9,7 +9,7 @@ keywords: 'Cohere API, large language models, generative AI'
 createdAt: 'Wed Nov 27 2024 00:00:00 GMT+0000 (Coordinated Universal Time)'
 updatedAt: 'Wed Nov 27 2024 00:00:00 GMT+0000 (Coordinated Universal Time)'
 ---
-Find information around deprecated endpoints and models with their recommended replacements. 
+Find information around deprecated endpoints and models with their recommended replacements. All deprecation announcements applies to models being accessed through our API. It does not apply to models served/hosted/deployed outside our API, where ad-hoc deprecation policies apply.


I don't think we should say "ad-hoc deprecation policies apply".

Instead say something like, "Please refer to partner documentation for deprecation policy on specific partner platforms."

co-sudip

We need to either limit this to "Model Deprecations" or add some more content to specific "Product Deprecations" beyond the model itself -- including things like chat.cohere.com or endpoints like generate/summarize or finetuning.

co-sudip · 2024-12-17T05:32:36Z

fern/pages/going-to-production/deprecations.mdx

@@ -21,10 +21,46 @@ Cohere uses the following terms to describe the lifecycle of our models:
 - **Deprecated:** The model and endpoints are no longer available to new customers but remain available to existing users until retirement. (An existing user is defined as anyone who has used the model or endpoint within 90 days of the deprecation announcement.) A shutdown date will be assigned at that time.


I like the existing user only caveat, but I am not sure if we have that ability today. Do we @manoj-cohere ?

co-sudip · 2024-12-17T05:39:21Z

fern/pages/going-to-production/deprecations.mdx

+| `embed-english-light-v2.0`                  | Embeddings    | N/A                        | Legacy         | N/A        | N/A      |
+| `embed-multilingual-v2.0`                   | Embeddings    | N/A                        | Legacy         | N/A        | N/A      |
+| `rerank-v3.5`                               | Rerankers     | 12/31/2025                 | Active         | N/A        | N/A      |
+| `rerank-english-v3.0                        | Rerankers     | 06/30/2025                 | Active         | N/A        | N/A      |


I think new users can continue to be onboarded to rerank v2.0 on Platform today.

yes I believe so

co-sudip · 2024-12-17T05:39:42Z

fern/pages/going-to-production/deprecations.mdx

+| `embed-english-v3.0`                        | Embeddings    | 06/30/2025                 | Active         | N/A        | N/A      |
+| `embed-english-light-v3.0`                  | Embeddings    | 06/30/2025                 | Active         | N/A        | N/A      |
+| `embed-multilingual-v3.0`                   | Embeddings    | 06/30/2025                 | Active         | N/A        | N/A      |
+| `embed-multilingual-light-v3.0`             | Embeddings    | N/A                        | Legacy         | N/A        | N/A      |


Why N/A for these?

I put N/A because we don't have a specified date for deprecation currently right?

github-actions · 2024-12-17T15:01:28Z

🌿 Preview your docs: https://cohere-preview-a4cabc31-2ede-42e3-9fdd-401dd7db28ae.docs.buildwithfern.com

added notes on deprecation policy

7507251

mahjongmen requested a review from a team as a code owner December 9, 2024 14:05

manoj-cohere reviewed Dec 16, 2024

View reviewed changes

co-sudip reviewed Dec 17, 2024

View reviewed changes

reflect comments

22c1c25

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

added notes on deprecation policy #288

added notes on deprecation policy #288

mahjongmen commented Dec 9, 2024 •

edited by cohere-pr-pal bot

Loading

github-actions bot commented Dec 9, 2024

manoj-cohere Dec 16, 2024

mahjongmen Dec 17, 2024

manoj-cohere Dec 16, 2024

mahjongmen Dec 17, 2024

manoj-cohere Dec 16, 2024

mahjongmen Dec 17, 2024

manoj-cohere Dec 16, 2024

mahjongmen Dec 17, 2024

co-sudip Dec 17, 2024

mahjongmen Dec 17, 2024

co-sudip left a comment

co-sudip Dec 17, 2024

co-sudip Dec 17, 2024

mahjongmen Dec 17, 2024

co-sudip Dec 17, 2024

mahjongmen Dec 17, 2024

github-actions bot commented Dec 17, 2024

		@@ -21,10 +21,46 @@ Cohere uses the following terms to describe the lifecycle of our models:
		- Deprecated: The model and endpoints are no longer available to new customers but remain available to existing users until retirement. (An existing user is defined as anyone who has used the model or endpoint within 90 days of the deprecation announcement.) A shutdown date will be assigned at that time.

added notes on deprecation policy #288

Are you sure you want to change the base?

added notes on deprecation policy #288

Conversation

mahjongmen commented Dec 9, 2024 • edited by cohere-pr-pal bot Loading

Changes:

github-actions bot commented Dec 9, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Anthropic

Open AI

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

co-sudip left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

github-actions bot commented Dec 17, 2024

mahjongmen commented Dec 9, 2024 •

edited by cohere-pr-pal bot

Loading