@@ -227,8 +227,9 @@ rules before submitting a pull request:
227227 :file: `doc/users/next_whats_new/README.rst ` for more information).
228228
229229* If you change the API in a backward-incompatible way, please document it in
230- :file: `doc/api/api_changes `, by adding to the relevant file
231- (see :file: `doc/api/api_changes.rst ` for more information)
230+ :file: `doc/api/next_api_changes/behaviour `, by adding a new file with the
231+ naming convention ``20202-02-17-JMK.rst `` where the date is followed by the
232+ contributor's initials.
232233
233234* See below for additional points about :ref: `keyword-argument-processing `, if
234235 applicable for your pull request.
@@ -317,8 +318,10 @@ API changes
317318Changes to the public API must follow a standard deprecation procedure to
318319prevent unexpected breaking of code that uses Matplotlib.
319320
320- - Deprecations must be announced via an entry in
321- the most recent :file: `doc/api/api_changes_X.Y `
321+ - Deprecations must be announced via a new file in
322+ the most recent :file: `doc/api/next_api_changes/deprecations/ ` with
323+ naming convention ``2020-01-01-JMK.rst `` where ``JMK `` are the contributor's
324+ initials.
322325- Deprecations are targeted at the next point-release (i.e. 3.x.0).
323326- The deprecated API should, to the maximum extent possible, remain fully
324327 functional during the deprecation period. In cases where this is not
0 commit comments