Topic/release notes 0.2.0 #503
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
Currently I'm unable to get through a clean cross-build for 2.10 and 2.11 with both JVM and JS. Even using additional memory (4G) I seem to run out late in the 2.11 build/test after building and testing 2.10. This suggests a memory leak in SBT or scalac. If we remove the clean, I should be able to "stage" the release by building ahead of time. The commit also removes parallel execution from the JS step for the same reason.
I reviewed the git logs since v0.1.2 to find the relevant commits, manually checked the commit authors against our current list, and tried to summarize the work and changes that users should expect to see. For reference, the command I used was `git log v0.1.2..HEAD`.
Current coverage is
|
| * `Choice[F[_, _]]` | ||
| * `Group[A]` | ||
| * `MonadReader[F[_, _], R]` | ||
| * `Stream[A]` and `StreamT[F[_], A]` |
|
👍 LGTM |
|
👍 thanks! |
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.
I reviewed the git logs since v0.1.2 to find the relevant commits,
manually checked the commit authors against our current list, and
tried to summarize the work and changes that users should expect
to see.
For reference, the command I used was
git log v0.1.2..HEAD.(This PR also includes the version tags, and a change I needed to
make for the build to succeed.)