-
Notifications
You must be signed in to change notification settings - Fork 452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Django 1.11 to 2.2 support #568
Comments
Would like to contribute as a code contributor on this feature. |
That's not a sustainable solution IMHO and from previous experience. |
@auvipy A fundraiser seems like a good idea. As it stands, what's currently missing / would be a new feature from Django 1.11/2.2 support? Is there list / issue thread of stuff that funding would go to? |
work on celery 3.x branch for some new releases with numerous bug fix and some new features needed for smoother migration to celery 4.x and Django-celery working with them. in a nutshell |
could you plz provide a sponsor link to pay? |
@auvipy Place where we can find the list of bugs/feature needed in Django-celery for celery 3.x for smoother migration to celery 4.x? |
I'd be happy to support if you have a description of the project and estimate of the cost. |
can you drop a line? [email protected] |
Has any head way been made ? I have some time I could contribute as well. I am working on an old project using djcelery and would like to update it. |
Also happy to chip in if needed. |
Looks like the functionnalities have been incorporated into different projects: https://github.com/celery/django-celery-results hopes this helps. Edit: its works alright. |
it's for celery 3.x series only. those two are for celery 4.x series+ |
we might add django 1.11 support to ease the migration |
I am looking for a few sponsors to work on these features:
https://opencollective.com/celery
The text was updated successfully, but these errors were encountered: