Context

Information

• Our versioning follows closely to the Django release process. The first two delimited values map to the release version of Django the version of the library is meant to support. I.e. `django-mongodb-backend==5.0.` supports `django==5.0.` and `django-mongodb-backend==5.1.3` would support working for `django==5.1.`. However, there is no guarantee `django-mongodb-backend==5.2.` will work with `django==5.1.` or `django==5.0.`
• Anything after the second dot delimiter is meant to reference patches made to the `django-mongodb-backend` itself. It's always advised when making a new project to use the latest version.
• For PyMongo Support, `django-mongodb-backend` works for the minimum PyMongo version 4.6
• As for MongoDB server support, `django-mongodb-backend` for both `5.0.x` and `5.1.x` will work from MongoDB Server Version 5.0 to Server Version 8.0.
• Our backend connects to the database using PyMongo, so please check your PyMongo version and see the compatibility matrix (https://www.mongodb.com/docs/languages/python/pymongo-driver/current/compatibility/#compatibility) for PyMongo to understand the server versions our framework supports.

• `django-mongodb-backend` currently supports Python 3.10, 3.11 and 3.12

Compatibility Matrix Boiled Down

• django-mongodb-backend Python Version Support: 3.10, 11 and 12 (Limitation is from Django's support being 3.10)
• General Guidance: minimum of whatever Python version Django and MongoDB support
• PyMongo Python Support: 3.8 | 3.9 | 3.10 | 3.11 | 3.12 | 3.13
• Django Python Support: 3.10 | 3.11 | 3.12

• MongoDB SERVER: 5.0, 6.0, 7.0, 8.0
• General Guidance: Check PyMongo MongoDB SERVER support

• Django Library version support: 5.0 and 5.1
• PyMongo Library version support: 4.6 | 4.7 | 4.8 | 4.9 | 4.10 | 4.11

Definition of done

What must be done to consider the task complete?

Pitfalls

What should the implementer watch out for? What are the risks?