Skip to content

Commit

Permalink
docs(python): Update deprecation period example
Browse files Browse the repository at this point in the history
  • Loading branch information
stinodego committed Feb 6, 2024
1 parent 6ab6550 commit 5d8fd95
Showing 1 changed file with 1 addition and 4 deletions.
5 changes: 1 addition & 4 deletions docs/development/versioning.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,10 +80,7 @@ Such changes will not be warned for, but _will_ be included in the changelog and
### Deprecation period

As a rule, deprecated functionality is removed two breaking releases after the deprecation happens.
For example:

- Before the release of `1.0.0`: a function deprecated in version `0.18.3` will be removed in version `0.20.0`
- After the release of `1.0.0`: a function deprecated in version `1.2.3` will be removed in version `3.0.0`
For example, a function deprecated in version `1.2.3` will be removed in version `3.0.0`.

This means that if your program does not raise any deprecation warnings, it should be mostly safe to upgrade to the next breaking release.
As breaking releases happen about once every three months, this allows three to six months to adjust to any pending breaking changes.
Expand Down

0 comments on commit 5d8fd95

Please sign in to comment.