Hey Uri. We’re not going to patch 3.0 now. (Risk of regression is too high — it’s why we have the backporting policy.)
It’s 3.1’s job to be “forward compatible” - folks should be able to update. This is a difficult case in that it requires allowing running the old version at the same time as the new one, which isn’t something I’d like to encourage, but I agree with Simon on the issue, we need to provide a path. Kind regards, Carlton On Fri, 31 Jul 2020 at 17:31, אורי <u...@speedy.net> wrote: > Hi Carlton, > > I think a possible solution can be if Django 3.0 will be patched to handle > sessions created by 3.1. This will allow both downgrading Django and > running Django on several servers with 3.0 and 3.1 in parallel. If this is > too late now to do it before releasing 3.1, maybe you can postpone this > change (of hashing algorithm, if I understand correctly) to Django 3.2. And > then of course, patch 3.0 and 3.1 to handle sessions created by 3.2. > > אורי > u...@speedy.net > > > On Fri, Jul 31, 2020 at 2:13 PM Carlton Gibson <carlton.gib...@gmail.com> > wrote: > >> Hi Uri. >> >> On 31 Jul 2020, at 12:11, אורי <u...@speedy.net> wrote: >> >> On Fri, Jul 31, 2020 at 12:28 PM Mariusz Felisiak < >> felisiak.mari...@gmail.com> wrote: >> >>> Markus reported a release blocker #31842 >>> <https://code.djangoproject.com/ticket/31842>related with running an >>> app on multiple servers with different versions of Django (3.0.x or 3.1). >>> >>> >> >> I think it might be related to an issue I reported - #31592 >> <https://code.djangoproject.com/ticket/31592>. Django 3.0 can't handle >> sessions created by Django 3.1. >> >> >> Yes, it’s related. Your issue was downgrading IIRC. This is “can’t >> upgrade piecemeal” — but a solution may allow your use-case too. >> >> C. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-developers+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/AEC8D4F2-E042-4A6B-9E9D-7D0584BB42B4%40gmail.com >> <https://groups.google.com/d/msgid/django-developers/AEC8D4F2-E042-4A6B-9E9D-7D0584BB42B4%40gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CABD5YeEVhj2T0Yq0q%3DESvKjEHfXddiTNtgo_M%2B%2BxDvSKs5xRYw%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CABD5YeEVhj2T0Yq0q%3DESvKjEHfXddiTNtgo_M%2B%2BxDvSKs5xRYw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJwKpyRKgSEmUH%2BZmtyC-6SFyZmTXNR7i3FVcoy5ik1azLjg3g%40mail.gmail.com.
