Skip to content

Conversation

felixxm
Copy link
Member

@felixxm felixxm commented Jul 9, 2020

#12333 with final edits.

Copy link
Contributor

@ferrants ferrants left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit: 🚢 Thanks!

@felixxm felixxm merged commit 7d6916e into django:master Jul 9, 2020
@felixxm felixxm deleted the pr/12333 branch July 9, 2020 18:46
@ticosax
Copy link
Contributor

ticosax commented Jul 10, 2020

👏

@urmanbm
Copy link

urmanbm commented Dec 10, 2020

Hi @ferrants, are there any plans moving it to release? If yes, when could it potentially happen?

It was merged into master on 9th of July when 3.0 was still in mainstream support. But I don't see it neither in 3.0 nor in 3.1.

Our team uses this feature. We have our own django 2.2 fork with this feature cherrypicked. Now we plan migrating to 3.1. If this feature would be released we would prefer using official django 3.1 rather than forking own version. This way we could receive patch releases automatically.

@felixxm @ticosax Huge thanks for implementing it

@felixxm
Copy link
Member Author

felixxm commented Dec 10, 2020

@borismu We don't backport new features after an alpha release. This feature will be available in Django 3.2+.

@urmanbm
Copy link

urmanbm commented Dec 10, 2020

@felixxm Thank you for prompt response!

Looking forward to Django 3.2 then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants