Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

APE 2: Clarify next major release meaning in deprecation policy #109

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

APE 2: Clarify next major release meaning in deprecation policy #109

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ae2175e
APE 2: Clarify next major release meaning
pllim Aug 27, 2024
cda56d1
APE 2: Rephrase based on feedback
pllim Aug 28, 2024
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
3 changes: 2 additions & 1 deletion APE2.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,8 @@ The guidelines in relation to API changes and backward compatibility are as foll
* New deprecations should not be introduced in bugfix releases.
* If developers wish to make an API change at a point in time where the next
release is a major release, they should introduce the deprecation in the major
release and carry out the change in the following major release.
release and carry out the change in the following major release
(i.e., the next x.0.0 that is at least a year away).
* The following will not be considered to be part of the API and can therefore
be changed in bugfix and minor releases:

Expand Down