You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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>
Copy file name to clipboardExpand all lines: spec-0000/index.md
+13-2Lines changed: 13 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: "SPEC 0 — Minimum Supported Versions"
2
+
title: "SPEC 0 — Minimum Supported Dependencies"
3
3
date: 2020-12-17
4
4
author:
5
5
- "Andreas C. Mueller <andreas.mueller.ml@gmail.com>"
@@ -24,7 +24,7 @@ endorsed-by:
24
24
25
25
## Description
26
26
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.
28
28
29
29
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).
30
30
@@ -33,12 +33,23 @@ Specifically, we recommend that:
33
33
1. Support for Python versions be dropped **3 years** after their initial release.
34
34
2. Support for core package dependencies be dropped **2 years** after their initial release.
35
35
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
+
36
43
### Core Project Endorsement
37
44
38
45
<!--
39
46
Briefly discuss what it means for a core project to endorse this SPEC.
40
47
-->
41
48
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.
0 commit comments