Switch to bi-annual deprecation policy

Co-authored-by: Jannis Leidel <jannis@leidel.info>

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 |