blob: a41733e4707b96220c36a79ef7a5e20253260581 [file] [log] [blame]
Manuel Pégourié-Gonnardf5acfba2021-04-26 09:57:40 +02001Please add your migration guide entries here. Until 3.0 is released, each PR
2that makes backwards-incompatible changes should add a file here, with the
3extension .md, a descriptive name and the following format:
Manuel Pégourié-Gonnardb2a10432021-04-23 11:59:00 +02004
Manuel Pégourié-Gonnardf5acfba2021-04-26 09:57:40 +02005---%<------%<------%<------%<------%<------%<------%<------%<---
Manuel Pégourié-Gonnardb2a10432021-04-23 11:59:00 +02006
Manuel Pégourié-Gonnard438ac272021-05-04 13:06:34 +02007The change that was made
Manuel Pégourié-Gonnardf5acfba2021-04-26 09:57:40 +02008------------------------
9
10Who exactly is affected: does this affect users of the default config, of a
11particular feature? Remember to contextualise.
12
13If I'm affected, what's my migration path? How should I change my code if this
Manuel Pégourié-Gonnard72f762b2021-05-04 11:24:49 +020014is an API change; if a feature was removed what are my alternatives?
Manuel Pégourié-Gonnardf5acfba2021-04-26 09:57:40 +020015
16---%<------%<------%<------%<------%<------%<------%<------%<---
17
Manuel Pégourié-Gonnard72f762b2021-05-04 11:24:49 +020018PRs that make multiple independent changes should include one entry for each
19changes or logical groups of changes. You can either add multiple files or put
20multiple entries in the same file.
21
Manuel Pégourié-Gonnardf5acfba2021-04-26 09:57:40 +020022For examples, have a look a docs/3.0-migration-guide.md (which includes the
23top-level header and an intro before the list of entries).
24
25As part of release preparation, the entries in this directory will be appended
26to docs/3.0-migration-guide.md and then re-ordered and reviewed one last time.
Manuel Pégourié-Gonnard72f762b2021-05-04 11:24:49 +020027The file is then going to be moved to the version-independent docs repo.