Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions spec-0000/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,16 @@ For instance, if a newer minimum version of a core package is needed by a projec
which is not backported to older versions.
{{< /admonition >}}

{{< admonition note >}}
Certain projects (e.g., projects that have more resources) may wish to provide long-term support (LTS) of an additional year.

Specifically, for projects wishing to provide LTS we recommend that:
Copy link
Contributor

@mdhaber mdhaber May 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The first sentence is that all projects should adopt a common policy. This goes against that, so I think we should acknowledge the discrepancy in some way. If we do not recommend one over the other, the first sentence might change to be "adopt one of two time-based poicies...". If we have a preference for the first but recognize the need for the other, we might say something to that effect here.


1. Support for Python versions be dropped **4 years** after their initial release.
2. Support for core package dependencies be dropped **3 years** after their initial release.

{{< /admonition >}}

### Core Project Endorsement

<!--
Expand Down Expand Up @@ -84,6 +94,10 @@ The situation has since improved due to improved installations via binary wheels

### Support Window

{{< admonition note >}}
For LTS, add 1 year to the support window.
{{< /admonition >}}

```mermaid
{{< include-raw "chart.md" >}}
```
Expand Down