Closed buske closed 7 years ago
Moving forward to a 1.1 release! \o/
In a follow up to my previous comment, it wouldn't hurt if we create a release branch for the release, fix issues, then merge back into master and tag the release (a la gitflow). Tagging the release will generate a new DOI number FYI!
Fine with me.
@Relequestual Sorry for straying from git flow. I've updated this PR (and others) to merge into a release/v1.1
branch (based off of the old master, not develop). Once we release v1.1, we'll make a new develop from that and try to follow more carefully.
@buske It's not always easy to keep to unless you're doing it daily anyway. I personally do it with my personal project also, for sanity reasons.
Great! It can really pay off in some situations! =]
The following backwards-compatible changes were agreed to a while back and merged into the develop branch. I propose we add them to master for a 1.1 release of the API.