#31842: django.core.signing.dumps() and loads() not backwards compatible
-----------------------------------+--------------------------------------
Reporter: Markus Holtermann | Owner: nobody
Type: Bug | Status: new
Component: Core (Other) | Version: 3.1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Comment (by Simon Charette):
> I'm skeptical that Django should facilitate running multiple Django
versions concurrently.
I think we should allow find a way to multi-node upgrades to happen just
like we do with `pickle_version` for anything that uses `pickle.dumps`.
Large project Django upgrades are often
[https://landing.google.com/sre/workbook/chapters/canarying-releases/
tentatively deployed through canarying] and eventually rolled out to
multiple nodes gradually (pods, dynos, etc.).
Not having a way to a graceful roll out of a version should be considered
a release blocker IMO.
--
Ticket URL: <https://code.djangoproject.com/ticket/31842#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.9f5270eebb1a9f7a52b82567708833c2%40djangoproject.com.
