Improve Robo version management #492
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
…rsion, do the release, and put the version back to '-dev' again.
DavertMik
approved these changes
Nov 15, 2016
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.
Overview
This pull request:
Summary
Keep the version at '-dev' between releases
Description
To reduce confusion, this PR ensures that the Robo version will always end in '-dev' between releases. The '-dev' modifier is removed during the release process, and put back again at the end. The --beta flag is still supported; it will advance through beta1, beta2 and so on, if used.
Major and minor version advances will still need to be done by hand prior to release.
Changes are all to the main RoboFile, which has no tests; therefore, there are no tests in this PR either.