1
1
Fork 0
mirror of https://github.com/pypa/pip synced 2023-12-13 21:30:23 +01:00

Add the deprecation policy changes from fde9eb66f0

This commit is contained in:
Pradyun Gedam 2018-07-17 13:59:41 +05:30
parent 1933dacc89
commit 3c073f92f4
No known key found for this signature in database
GPG key ID: DA17C4B29CB32E4B

View file

@ -34,19 +34,19 @@ reworked and resubmitted for the next release.
Deprecation Policy Deprecation Policy
================== ==================
Any change to pip that removes or significantly alters user-visible behaviour Any change to pip that removes or significantly alters user-visible behavior
that is described in the pip documentation will be deprecated for a minimum of that is described in the pip documentation will be deprecated for a minimum of
one released version before the change occurs. Deprecation will take the form of 6 months before the change occurs. Deprecation will take the form of a warning
a warning being issued by pip when the feature is used. Longer deprecation being issued by pip when the feature is used. Longer deprecation periods, or
periods, or deprecation warnings for behaviour changes that would not normally deprecation warnings for behavior changes that would not normally be covered by
be covered by this policy, are also possible depending on circumstances, but this policy, are also possible depending on circumstances, but this is at the
this is at the discretion of the pip developers. discretion of the pip developers.
Note that the documentation is the sole reference for what counts as agreed Note that the documentation is the sole reference for what counts as agreed
behaviour. If something isn't explicitly mentioned in the documentation, it can behavior. If something isn't explicitly mentioned in the documentation, it can
be changed without warning, or any deprecation period, in a pip release. be changed without warning, or any deprecation period, in a pip release.
However, we are aware that the documentation isn't always complete - PRs that However, we are aware that the documentation isn't always complete - PRs that
document existing behaviour with the intention of covering that behaviour with document existing behavior with the intention of covering that behavior with
the above deprecation process are always acceptable, and will be considered on the above deprecation process are always acceptable, and will be considered on
their merits. their merits.