Use Versioneer and add HOW_TO_RELEASE #311
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Good call @spencerkclark. Any other edits? Otherwise will merge this later today. |
spencerkclark
approved these changes
Nov 14, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In anticipation of the v0.3 release (#307), this PR does two things (arguably more appropriately two separate PRs, but since they both relate to releasing I figured it's fair):
C.f. Versioneer pydata/xarray#2163, use Versioneer to simplify keeping track/updating version number. I basically followed how xarray did it exactly, including copying in the versioneer code directly into our codebase (Versioneer is public domain, so there's no worry re: licensing) rather than making it a dependency.
Add a HOW_TO_RELEASE document, again copied nearly verbatim from xarray's. NOTE: this includes the use of stable and master branches, rather than our current use of master and develop. But since we will be making that switch when we bump to v0.3 anyways (Use
stableandmasteras our two main branches, rather thanmasteranddevelop#308), and this document is mostly for my own reference anyways, I figure it's OK for it to leave it as is for now.