Skip to content

Commit 6a8458f

Browse files
jarrodmillmanstefanvCarreaubsipocz
authored
Clarify whether core packages are required to make bug-fix releases (#297)
--------- Co-authored-by: Stefan van der Walt <sjvdwalt@gmail.com> Co-authored-by: M Bussonnier <bussonniermatthias@gmail.com> Co-authored-by: Brigitta Sipőcz <b.sipocz@gmail.com>
1 parent 9209c89 commit 6a8458f

1 file changed

Lines changed: 13 additions & 2 deletions

File tree

spec-0000/index.md

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "SPEC 0 — Minimum Supported Versions"
2+
title: "SPEC 0 — Minimum Supported Dependencies"
33
date: 2020-12-17
44
author:
55
- "Andreas C. Mueller <andreas.mueller.ml@gmail.com>"
@@ -24,7 +24,7 @@ endorsed-by:
2424

2525
## Description
2626

27-
This SPEC recommends that all projects across the Scientific Python ecosystem adopt a common time-based policy for dropping support of older Python and core package versions.
27+
This SPEC recommends that all projects across the Scientific Python ecosystem adopt a common time-based policy for dropping dependencies. From the perspective of this SPEC, the dependencies in question are core packages as well as older Python versions.
2828

2929
All versions refer to feature releases (i.e., Python 3.8.0, NumPy 1.19.0; not Python 3.8.1, NumPy 1.19.2).
3030

@@ -33,12 +33,23 @@ Specifically, we recommend that:
3333
1. Support for Python versions be dropped **3 years** after their initial release.
3434
2. Support for core package dependencies be dropped **2 years** after their initial release.
3535

36+
{{< admonition note >}}
37+
Core packages may or may not decide to provide bug fix releases during the full 2 year period after release.
38+
Therefore, projects may occasionally want to drop support for core package dependencies earlier than recommended by this SPEC.
39+
For instance, if a newer minimum version of a core package is needed by a project due to a critical bug fix,
40+
which is not backported to older versions.
41+
{{< /admonition >}}
42+
3643
### Core Project Endorsement
3744

3845
<!--
3946
Briefly discuss what it means for a core project to endorse this SPEC.
4047
-->
4148

49+
Core project endorsing this SPEC means that those projects encourage all projects across the Scientific Python ecosystem
50+
to limit how long they support older Python versions and older dependency versions.
51+
A core project endorsing this SPEC does **not** imply that that project will provide bug-fix releases for two full years after a release.
52+
4253
### Ecosystem Adoption
4354

4455
<!--

0 commit comments

Comments
 (0)