You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello @browniebroke thanks for this project it looks promising! I believe it can greatly accelerate the speed of adoptions of newly released versions of Django.
I was wondering if you'd be interested in receiving contributions for migration to versions between Django 1.11 LTS and 2.2 LTS. Even if these versions are not supported anymore I think it could be of interest to a lot of developers who are still in the process of upgrading.
I currently work for a company that is the process of doing so and also has a few Django 1.9/1.10 deprecation warnings that need to be addressed on a large project. Since we'll have to automate the process anyway I was wondering if you'd be interested in receiving contributions for these versions as well.
The text was updated successfully, but these errors were encountered:
Yes, I would definitely accept these contributions for these. We are running 2.2 at work, so earlier versions were not my primary use case, hence I focused on 3.0+.
I think it makes to support at least from 1.11 which has just gone out of support and I assume lot of people are still using.
Description
Hello @browniebroke thanks for this project it looks promising! I believe it can greatly accelerate the speed of adoptions of newly released versions of Django.
I was wondering if you'd be interested in receiving contributions for migration to versions between Django 1.11 LTS and 2.2 LTS. Even if these versions are not supported anymore I think it could be of interest to a lot of developers who are still in the process of upgrading.
I currently work for a company that is the process of doing so and also has a few Django 1.9/1.10 deprecation warnings that need to be addressed on a large project. Since we'll have to automate the process anyway I was wondering if you'd be interested in receiving contributions for these versions as well.
The text was updated successfully, but these errors were encountered: