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

zest.releaser upgrade? #82

Open
brainwane opened this issue Mar 14, 2018 · 2 comments
Open

zest.releaser upgrade? #82

brainwane opened this issue Mar 14, 2018 · 2 comments

Comments

@brainwane
Copy link

Hi! I'm one of the maintainers of Twine. I was checking out the libraries.io usage list for twine and happened to notice that your requirements.txt file specifies an old version. The new version of Twine is 1.10.0. Anything we can do to make your upgrade path easier?

Thanks!

@charleso
Copy link
Owner

Hi @brainwane, thanks for reaching out. I guess I'm technically the maintainer of git-cc, but I haven't used it in over 7 years so I basically just accept patches from people. I'm afraid to say there is no testing in git-cc so it's fairy hard to change anything without having a live clearcase server to test against. :(

@brainwane brainwane changed the title Twine upgrade? zest.releaser upgrade? Jun 7, 2018
@brainwane
Copy link
Author

@charleso OK, I understand. I see that twine is not actually used anywhere in your codebase; it's used by zest.releaser, a tool the maintainer can use to upload the package to PyPI. So upgrading Twine and zest.releaser won't affect the ClearCase-related code at all.

Twine's now at version 1.11.0 (changelog). And zest.releaser is at 6.15.0. I encourage you to upgrade and to use Test PyPI to try uploading your package to PyPI with the new tooling!

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

2 participants