From b0d2face654e0be271371be8509608be6037f714 Mon Sep 17 00:00:00 2001 From: Maximilian Roos <5635139+max-sixty@users.noreply.github.com> Date: Thu, 28 Sep 2023 10:24:57 -0700 Subject: [PATCH] Make the dependencies part explicit (#269) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Clarify that the recommendation is about "how long new releases of a package should permit older versions of dependencies", not the more conventional meaning of support as "we fix bugs for old versions" — like most medium-sized open-source projects, we (xarray) only release fixes for the current version of xarray ref https://github.com/pydata/xarray/discussions/8237#discussioncomment-7126175 @andersy005 @shoyer @dcherian (added by @jarrodmillman ) --------- Co-authored-by: Jarrod Millman --- spec-0000/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spec-0000/index.md b/spec-0000/index.md index ea2ff8ec..8017c5a2 100644 --- a/spec-0000/index.md +++ b/spec-0000/index.md @@ -29,8 +29,8 @@ All versions refer to feature releases (i.e., Python 3.8.0, NumPy 1.19.0; not Py Specifically, we recommend that: -1. Support for a given version of Python be dropped **3 years** after its initial release. -2. Support for a given version of other core packages be dropped **2 years** after their initial release. +1. Support for Python versions be dropped **3 years** after their initial release. +2. Support for core package dependencies be dropped **2 years** after their initial release. ### Core Project Endorsement