Skip to content

added versioneer for versioning #150

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

Merged
merged 1 commit into from
Apr 20, 2016
Merged

Conversation

alorenzo175
Copy link
Contributor

Versioneer is nice because you never have to (or forget to) update the __version__ string. To make a new release version, you just add a git tag. When changes are made after a tag, the git commit is indicated in the version, so it might be something like 0.3.0+17.g39a420e indicating the code is based on git commit 39a420e which is 17 commits after the 0.3.0 tag.

The versioneer code is kept in _version.py so that version.py can be left alone for backwards compatibility. This seems kind of redundant, but might help a few people.

@wholmgren
Copy link
Member

Thanks, I've wanted this a few times recently. Add a note and your name to the 0.3.1 whatsnew.

The versioneer code is kept in _version.py so that version.py can
be left alone for backwards compatibility
@wholmgren wholmgren merged commit 1529188 into pvlib:master Apr 20, 2016
@wholmgren
Copy link
Member

For future reference, also see also commit 73e1df1

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

Successfully merging this pull request may close these issues.

2 participants