Merge pull request #228 from RadicalFx/release/1.6.0 #230
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
Release/1.6.0
|
this should be ready to go, I'll wait for the build and then auto-merge, no real changes simply reverse merging after release. |
|
the only problem with the reverse merge is this:
is what we should expect? do we care about? |
|
Same question I was asking myself, from a certain perspective yes, the next build of develop after we merge a release should result in a higher version then what we just released. However I'm wondering what this setting does. The documentation is not that clear or I'm misinterpreting it, anyway I need to play with it a little bit. |
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.
Reverse merge Release/1.6.0