-
Notifications
You must be signed in to change notification settings - Fork 60
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
Release managing #142
Comments
Hi Tobias, sure, handle is "Ede_123". Safes us both some effort as I don't have to bug you whenever I think it's a good time for a new release 😉 A new 0.36 release is in fact due soon. I just wanted to give the recent precision changes a little testing time and also look into the last remaining filed bug if time permits. Long term goal for me would be to finalize #121 / fix #119 (add API) and then release version 1.0.0 (and switch to semantic versioning) once finished. (Will still take some time and thought though, i.e. I already changed my mind again since doing the PR). |
Sounds cool! I've given you "Maintainer" role on Scour/PyPI, which allows you to push new releases. If it doesn't work, feel free to reopen .. |
Just pushed Scour 0.36. Seems to have worked fine (except for some issues with pushing the package, likely due to pypa/setuptools#941). Hope I didn't miss anything... |
Looks good! It is avail on https://pypi.python.org/pypi/scour |
@Ede123 last release on PyPI was 0.35 (https://pypi.python.org/pypi/scour), but you've been quite active over the months;) Do you want admin role on scour on PyPI so you can push releases?
If so, what is your PyPI handle?
Note to self: https://pypi.python.org/pypi?:action=role_form&package_name=scour
The text was updated successfully, but these errors were encountered: