Skip to content
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

Make a release #70

Closed
rgbkrk opened this issue Nov 21, 2016 · 16 comments
Closed

Make a release #70

rgbkrk opened this issue Nov 21, 2016 · 16 comments

Comments

@rgbkrk
Copy link
Member

rgbkrk commented Nov 21, 2016

Hey @ogrisel, @mrocklin, @pitrou!

We should make a release. I've made the last few, I'd love to have someone else take the reigns on shipping. Since I'm no longer using this package directly, I don't have much vested interest in getting this shipped (other than as a user of dask and pyspark).

@pitrou - what is your username on PyPI?

@pitrou
Copy link
Member

pitrou commented Nov 21, 2016

My username on PyPI is antoine.

@rgbkrk
Copy link
Member Author

rgbkrk commented Nov 21, 2016

Added you, thank you.

@pitrou
Copy link
Member

pitrou commented Nov 21, 2016

Are the steps required to make a release describe somewhere? A particular "setup.py" invocation perhaps?

@mrocklin
Copy link
Contributor

@rgbkrk is this just the following?

git clean -xfd
python setup.py sdist bdist_wheel --universal
twine upload dist/*

@rgbkrk
Copy link
Member Author

rgbkrk commented Nov 22, 2016

Seems about right

@ogrisel
Copy link
Contributor

ogrisel commented Nov 22, 2016

+1

@pitrou
Copy link
Member

pitrou commented Nov 22, 2016

Also bump the version number somewhere?

@ogrisel
Copy link
Contributor

ogrisel commented Nov 22, 2016

Yes and push a new tag to github as well.

@mrocklin
Copy link
Contributor

mrocklin commented Nov 25, 2016 via email

@pitrou
Copy link
Member

pitrou commented Nov 25, 2016

Perhaps #71 should be solved before making a new release.

@mrocklin
Copy link
Contributor

I plan to issue a new release of cloudpickle on PyPI and conda-forge tomorrow if no one raises any objections before then.

@mrocklin
Copy link
Contributor

mrocklin commented Jan 2, 2017

I've added Python 3.6 to the travis testing matrix, released version 0.2.2 to PyPI, and submitted a PR to the conda-forge feedstock. However, I don't have write permissions to the conda-forge repository so one of the current maintainers will have to merge conda-forge/cloudpickle-feedstock#6

@rgbkrk
Copy link
Member Author

rgbkrk commented Jan 2, 2017

Great, thanks Matthew.

@Peque
Copy link
Member

Peque commented Jul 26, 2017

Are there any blocking issues preventing a new release? Otherwise I would be interested in a new version that includes @ssanderson changes and the __transient__ support removal. 😊

If you are going to increase the major version due to the __transient__ change maybe it would be a good moment to officially drop Python 2.6 and 3.3 support?

@hugovk
Copy link
Contributor

hugovk commented Oct 28, 2017

This can be closed now.

Python 2.6 and 3.3 were dropped in #122 #125.

Cloudpickle v0.4.1 was released two days ago: https://github.com/cloudpipe/cloudpickle/releases

@rgbkrk rgbkrk closed this as completed Oct 28, 2017
@rgbkrk
Copy link
Member Author

rgbkrk commented Oct 28, 2017

Thanks for all the issue stewardship @hugovk! I'm going to add you to the repo to make it easier for you to close issues as part of triage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants