diff options
| author | Thomas A Caswell <tcaswell@gmail.com> | 2019-07-25 18:48:33 -0400 |
|---|---|---|
| committer | Thomas A Caswell <tcaswell@gmail.com> | 2019-07-25 18:49:32 -0400 |
| commit | 477ca0cf492eea17e979b4bec55f35f7e23788ae (patch) | |
| tree | a4da6bce11458f59d34c3d6195e6f6c4f4125b39 | |
| parent | 783b4eff6888738d9d8e0e70d27e79cda7426fc4 (diff) | |
| download | numpy-477ca0cf492eea17e979b4bec55f35f7e23788ae.tar.gz | |
DOC: define minor vs major vs patch version for this NEP
| -rw-r--r-- | doc/neps/nep-0029-deprecation_policy.rst | 31 |
1 files changed, 22 insertions, 9 deletions
diff --git a/doc/neps/nep-0029-deprecation_policy.rst b/doc/neps/nep-0029-deprecation_policy.rst index 787ad5eca..cfbdfad58 100644 --- a/doc/neps/nep-0029-deprecation_policy.rst +++ b/doc/neps/nep-0029-deprecation_policy.rst @@ -33,10 +33,23 @@ IPython, Jupyter, yt, SciPy, NumPy, and scikit-image. Detailed description -------------------- -When a project creates a new major or minor release, we recommend that the project should support all -minor versions of ``Python`` introduced and released in the prior 42 -months ~~from their anticipated release date~~ and all minor versions of -NumPy released in the prior 24 months. +For the purposes of this NEP we assume semantic versioning and define: + +*major version* + A release that change the first number (e.g. X.0.0) + +*minor version* + A release that changes the second number (e.g x.Y.0) + +*patch version* + A release that changes the third number (e.g. x.y.Z) + + +When a project creates a new major or minor version, we recommend that +the project should support all minor versions of ``Python`` introduced +and released in the prior 42 months ~~from their anticipated release +date~~ and all minor versions of NumPy released in the prior 24 +months. The diagram:: @@ -50,11 +63,11 @@ The diagram:: |-----------------------------------------> Dec19 |-----------------------------------------> Nov20 -shows the 42 month support windows for ``Python``. A project with a major or -minor release in Feb19 should support py35 and newer, a project with a -major or minor release in Dec19 should support py36 and newer, and a -project with a major or minor release in Nov20 should support py37 and -newer. +shows the 42 month support windows for ``Python``. A project with a +major or minor version release in Feb19 should support py35 and newer, +a project with a major or minor version release in Dec19 should +support py36 and newer, and a project with a major or minor version +release in Nov20 should support py37 and newer. The current Python release cadence is 18 months so a 42 month window ensures that there will always be at least two versions of ``Python`` |