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
1.4.0 Release Organization #159
Comments
So currently I have 3 bugs and one WIP PR that may be good to get resolved before a v1.4.0 release, but need to dig into them a bit further. Bugs:
WIP PR: |
It has to be noted that v1.4.0 also introduces braking changes: arguments |
Hm good point, probably should be a major release then. |
have you run |
It would be nice to pass 'check_estimator'. |
Hey @janmotl, do you happen to know when the new version would be released? If there are remaining tasks, I can help to close them if desired. |
@JohnnyC08 , don't you know how to deal with "errors" like:
as reported at: https://travis-ci.org/scikit-learn-contrib/categorical-encoding/jobs/491609594 ? |
@janmotl I will pull the latest master and see if I can reproduce locally |
Beside the failing Travis CI (I didn't manage to reproduce the error with nosetest on my local computer), the code should be ready for release 2.0.0. |
@janmotl sorry for the delay, I'll take a look at a 2.0.0 release here shortly. |
@janmotl actually, to avoid delays like this in the future, it'd probably make sense to add you as a collaborator on PyPI.org right? If you send me your PyPI username I can add you to the project there. |
Good. My PyPI username: |
@janmotl should be a maintainer there now, please check and let me know. |
Thank you, @wdm0006. I am now a maintainer. Do we have a procedure how to make a release? |
@janmotl not very formally, I usually just up the version in setup.py, run update_docs.sh and use twine to publish to pypi. Would you like to give that a shot and I can help out with any issues that crop up. |
Done. Could you check it? |
Looks good! |
Hey all, been away from the project for a bit, but I'm going back through all of the issues and PRs worked on recently (looks like a bunch of good progress!). Special thanks to @janmotl for all of the work as primary maintainer over the past months.
Our last release was 1.3.0 on October 14th. Since then ya'll have:
Which I think is a quite full set of features to constitute a release. I will be opening a separate issue to discuss how we as a community can improve our release cycle, but for now will be going through open issues and tagging anything that should be included before the v1.4.0 release. Any input on what should or shouldn't be completed prior to release is welcome.
Thank you all for the work and support this year, and Happy Holidays.
The text was updated successfully, but these errors were encountered: