Opened 10 years ago
Last modified 9 years ago
#24106 closed New feature
Document backwards incompatible changes to database backend API — at Initial Version
| Reported by: | Anssi Kääriäinen | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I believe we don't have a separate ticket for documenting backwards incompatible changes to database backend API. In duth it was agreed that we want to do this.
An idea of how to do this is to log/diff changes to Django's backends between stable/1.7 and master. Going through the changes in Django should give a good approximation of all the breaking changes (another place where breakage is possible is Compiler module).
If possible, I'd like to document the changes in a way that is both backwards and forwards compatible. That is, we give a replacement suggestion that works both in 1.7 and 1.8 (very likely conditional on Django version).
Note:
See TracTickets
for help on using tickets.