Do there any blockers to bump new release?

[jramnai]

We are looking forward to using enmerkar with Django 3.2 on edX.

Required PR - #4 is already merged into the master branch.
Do there any chance a new version will be bumped soon?

If any blockers with the release I would be happy to help.

Thank you in advance.

@tonybajan
@hazelw

[jramnai]

@tonybajan or @hazelw, can any of you make a new release on PyPI?

[jramnai]

@tonybajan @hazelw can you please look into this?

[tonybajan-globality]

I can't do this release (needs someone @ Zegocover) but the changes in #4 are only to CI/metadata. If you're having issues on Django 3.2 with the current version of the package, I don't think a new release will solve them?

[jramnai]

@natabene, FYI ^

[natabene]

@jramnai Thanks so much for the ping. Our team will look into this ASAP and provide feedback.

[mike-perdide]

Hi, are there any updates on this subject? We too would be interested in a new version supporting Django 3.2 🙂

[natabene]

@mike-perdide We were a bit side tracked, but will look into this soon.

[UsamaSadiq]

Hi @natabene
The currently available release 0.7.1 does have Django 3.2 support in it and we've already deployed edX with the previous version.
@tonybajan-globality thanks for your help on it. A new release is not a blocker for us now but it would be preferred to get the new metadata and changes.
Thanks @jramnai for your efforts in keeping track of this issue. I believe we can close this issue since a new release is not required immediately now.

[natabene]

@UsamaSadiq Per Jeremy, "'We'd still like to see a new release get made with explicit Django 3.2 support. I think it makes sense to keep the upstream ticket open, but tracking it isn't a top priority for us right now."

[hazelw]

I'm also no longer at Zego so can't push a new release to PyPI.

@stuartleigh @gregbeech @martyphee this library looks like it needs a decision made re: maintenance.