django-user-sessions
django-user-sessions copied to clipboard
jazzband
Possibility of a new Release
Thanks a lot for django-user-sessions. It has been working great for us.
I wanted to ask if it was possible to create a new release? It has been a while and a few patches have landed.
The main reason why I would prefer a new release is https://github.com/jazzband/django-user-sessions/pull/114, which made samesite cookie configuration possible. The current release defaults to None, which is not the Django default. This is probably my main gripe with it: You would expect the Django default, which is not the case.
Again thanks for caring about this project for such a long time!
I'd like to tag a new 2.0 release if there are no objections.
Jumping to 2.0 since there's breaking changes (mostly, dropping older Python version).
Any comments?
I think this is fine. If you have the time, it would be nice if the breaking changes were documented. But I would be fine with a new release in whatever version :).
A release would be nice to avoid such "hacks": https://github.com/jazzband/django-two-factor-auth/pull/566
Is there anything preventing the release?
Will tag a release after merging https://github.com/jazzband/django-user-sessions/pull/147
Is there anything preventing the release?
master doesn't work with Python 3.6. That Python is EOL, so we should drop it too.
Currently needing approval: https://github.com/jazzband/django-user-sessions/pull/149 and https://github.com/jazzband/django-user-sessions/pull/147
My review doesn't count. Would I need to become a member of jazzband for it to count?
Release tagged: https://github.com/jazzband/django-user-sessions/releases/tag/2.0.0
There's a wheel and source tarball ready.
I'll wait until the end of the day before pushing this to PyPI. If anyone wants to early test the above artefacts, feedback is welcome.
Oh, I'm only a member so can't release new versions, @ricco386 can you chime in?
Via https://jazzband.co/projects/django-user-sessions