-
-
Notifications
You must be signed in to change notification settings - Fork 873
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
Any plan for the official 3.0 release ? #967
Comments
You could try installing it directly from GitHub. |
This is not suitable for production applications :( |
Are there blockers to releasing 3.0 to PyPi? I'm happy to chip in to help package it. |
@RedneckEdamame have a look here if you want to contribute #896 |
@adehad @Addono @ssbarnea can we make a Todo list of what needs to be done for another pypi release? |
@studioj yeah I would be happy to |
Yep sounds like a plan. If we can get a new milestone for this release (I imagine 4.0.0 as we dropped support for a python version) we can also start tagging any pull requests we want merged in first. I think the key ones are those related to the new GDPR changes. e.g. #927 |
Done 3.0.1 minutes ago. Fixing the release pipeline took far more time than I was hopping. Those with review rights, please review open PRs, fix them or close them if original OP is not updating them. I also activated discussions, so we can move questions there and cleanup the issue tracker. |
I can only see beta on PyPi ?
The text was updated successfully, but these errors were encountered: