From 38bdc5e75a57f754e9539a72167b5427a7fe5613 Mon Sep 17 00:00:00 2001 From: Ken Odegard Date: Thu, 21 Jul 2022 08:46:56 -0500 Subject: [PATCH] Switch to bi-annual deprecation policy Co-authored-by: Jannis Leidel --- cep-deprecation.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/cep-deprecation.md b/cep-deprecation.md index 25501d01..2edc56ea 100644 --- a/cep-deprecation.md +++ b/cep-deprecation.md @@ -19,15 +19,15 @@ This CEP describes a deprecation schedule to properly warn about upcoming remova We propose a deprecation schedule that is slower than the Conda Release Schedule (CEP-?). This is in acknowledgment of our diverse user groups (e.g. everything from per user per machine installs to multi-user installs on shared clusters). -We define a new type of release, a deprecation release, to augment regular releases. A deprecation release occurs three (3) times every year in January, May, and September: +We define a new type of release, a deprecation release, to augment regular releases. A deprecation release occurs twice every year in March and September: | Version | Release Type | |---|---| -| `YY.1.0` | regular, **deprecation** | +| `YY.1.0` | regular | | `YY.2.0` | optional | -| `YY.3.0` | regular | +| `YY.3.0` | regular, **deprecation** | | `YY.4.0` | optional | -| `YY.5.0` | regular, **deprecation** | +| `YY.5.0` | regular | | `YY.6.0` | optional | | `YY.7.0` | regular | | `YY.8.0` | optional |