Revert "v1.0.0 (#1145)" #1231
Merged
Revert "v1.0.0 (#1145)" #1231
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
This reverts commit ca6963c. The `v1.0.0` branch was a long-running feature branch containing a large amount of disparate commits from many authors. It was squashed into a single commit prior to being merged to the project's `master` branch. For the purposes of attribution, reference, and history analysis, the composite commits should be preserved, and the branch should be incorporated into `master` via a dedicated merge commit.
|
Good call, wasn’t really paying this much attention when merging. |
|
@jugglinmike @fb55 any ETA on 1.0 release? |
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.
This reverts commit ca6963c.
The
v1.0.0branch was a long-running feature branch containing a largeamount of disparate commits from many authors. It was squashed into a
single commit prior to being merged to the project's
masterbranch.For the purposes of attribution, reference, and history analysis, the
composite commits should be preserved, and the branch should be
incorporated into
mastervia a dedicated merge commit.