OK, so for me, this should go into v2.2, but not v2.1 or v1.11. (I see you already backported to 2.2 so... 🙂)
My general take here is that we could be half-a-notch more generous backporting to the current version (e.g. 2.2 now) but should be just as strict as we are once a version is out of mainstream support. (Loosely: Given how easy the update process is these days, I don't think we do anyone any favours keep older versions on life-support...) C. On Thursday, 4 April 2019 14:52:23 UTC+2, Mariusz Felisiak wrote: > > Patch for adding support for psycopg2 *2.8* is ready (see ticket #30331 > <https://www.google.com/url?q=https%3A%2F%2Fcode.djangoproject.com%2Fticket%2F30331&sa=D&sntz=1&usg=AFQjCNHNa1KFMN7Kxeg3zENVtvCWjnF5_Q> > > and PR11171 <https://github.com/django/django/pull/11171>). Fix is quite > straightforward and works with all supported version of psycopg2, i.e. > *2.5.4+*. The question is, should we backport this fix to the *1.11.x* > and *2.1.x*? Theoretically it doesn't qualify due to our backport policy, > because both are in the "extended support" time. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/c7a802c5-c19a-41de-8283-abd742144541%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
