Remove metadata support

[RealOrangeOne]

Large changes like this will hit Django first, before being included in the backport.

[ldeluigi]

My issue with this is that you haven't provided a replacement for your users relying on this feature.

At the very least, please open a feature request to add metadata to django.tasks (I also wonder why it hasn't been done in the first place).
I used the metadata field to track progress, and it's not something weird or peculiar, it's more something most of django-tasks users wanted to do, and now it has become impossible.

[RealOrangeOne]

At the very least, please open a feature request to add metadata to django.tasks

That's a very entitled response.

I'm still working out how best to submit these kinds of large feature changes to django.tasks.

it's not something weird or peculiar

I completely agree. I built it on discussion with a friend who reminded me just how crucial the functionality is. The benefit is its versatility.

My issue with this is that you haven't provided a replacement for your users relying on this feature.

This is sadly true. For now, the work-around will be to store the metadata in a side channel - perhaps another model or cache. It's far from pretty, but given that even if there was a PR merged today with support, it wouldn't be usable for another 6 months.

[ldeluigi]

@RealOrangeOne may I suggest to write an initial proposal to https://github.com/django/new-features to spark an initial discussion with the community?