-
Notifications
You must be signed in to change notification settings - Fork 31
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
Create a new release of CVSAnaly: 2.2.0 / 3.0.0 #77
Comments
No feedback. Seems to be not important. |
@andygrunwald sorry for not taking care of this. I guess it is important/interesting. If you're still volunteering for that, just comment here, and I will help you as much as I can to do this. |
👍 My MSR class tried setting up this tool, but because some of us were on Ubuntu, some on OS X, and some on Windows, it was just a gong show. A |
For a tutorial I gave last year on CVSAnalY and the other MetricsGrimoire [1] http://gsyc.es/~grex/2015-sattose/bash_history.txt regards, Gregorio 2016-01-21 1:31 GMT+01:00 Eddie Antonio Santos [email protected]:
Gregorio Robles |
Hey,
the last release (2.1.0) is long time ago (ca. 2 years).
I would like to release a new (stable) version and upload it to pip (see #76).
The same i would like to suggest for RepositoryHandler.
I like to use a stable version in production and not the current master.
What do you think?
What steps are necessary to release a new version? Raise the version number, tagging in git and upload it to PyPi?
I can take care of it.
The text was updated successfully, but these errors were encountered: