[WIP] 3.0.0 #559
Merged
[WIP] 3.0.0 #559
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
|
Yeah, you can cut a release @shadowspawn. I have no problem with that. Let's use master as the release branch and protect develop. |
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.
Putting together next release. Are you happy with me cutting a release @troy0820 or would you like to do it?
I have created a
developbranch as in GitFlow branch naming. Sincen-installis using git directly, this lets us prepare before copying up tomasterwhere it could get picked up by some users immediately.See CHANGELOG for details of the changes already on
masterthat have not been released to npm yet, and a couple of the open Pull Requests. As well as tracking the changes, can copy and paste to fill in the Releases details in GitHub.