For the purpose of this document, 'minor version' is in the sense of

SemVer (major, minor, patch) and includes both major and minor

releases. For projects that use date-based versioning, every release

is a 'minor version'.

- support minor versions of ``Python`` initially released

36 months prior to our planned release date.

- support minor versions of ``numpy`` initially released in the 36

months prior to our planned release date or oldest that supports the

minimum python version (which ever is higher)

For python dependencies we should support at least:

minor versions initially released in the 36 months prior to our

planned release date or the oldest that support our minimum python +

numpy

minor versions initially released in the 24 months prior to our

planed release date or the oldest that supports our minimum python.

Test and Documentation Dependencies

As these packages are only needed for testing or building the docs and

not needed by end-users, we can be more aggressive about dropping

support for old versions. However, we need to be careful to not

over-run what down-stream packagers support (as most of the run the

tests and build the documentation as part of the packaging process).

We will support at least minor versions of the development

dependencies released in the 12 months prior to our planned release.

We will only bump these as needed or versions no longer support our

minimum Python and numpy.